From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] autoconf2.7
Date: Thu, 9 Dec 2021 11:11:13 -0500 [thread overview]
Message-ID: <0cab6c70-e8d1-a10f-94a5-b0eba4b2bb8d@cornell.edu> (raw)
In-Reply-To: <YbHZbmXD+312rot1@calimero.vinschen.de>
On 12/9/2021 5:24 AM, Corinna Vinschen wrote:
> On Dec 8 19:46, Achim Gratz wrote:
>> Achim Gratz writes:
>>> + case "${WANT_AUTOCONF}" in
>>> + 2.5|'')
>>> + WANT_AUTOCONF=2.5
>>> + case $(autoconf --version 2> /dev/null | head -n 1) in
>>> autoconf*2.[56]?) ;;
>>> *) error "autoconf2.5 is required to build this package" ;;
>>> + esac
>>> + ;;
>>> + 2.7)
>>> + WANT_AUTOCONF=2.7
>>
>> If anybody prefers cygport to default to 2.7, then the "|''" part of the
>> above patch needs to be moved to the pattern clause for 2.7.
>
> We should do that, IMHO.
I agree, as I already said in a different thread. Either way, there remains the
question of how to get cygport patched. Until that happens, no maintainers can
use autoconf 2.71 unless they patch cygport locally, and no SCALLYWAG builds can
use autoconf 2.71.
Yaakov, any chance you would accept a co-maintainer of cygport (Jon Turney seems
like the obvious choice if he's willing) so that we can move forward on this and
other patches that have been proposed?
Ken
next prev parent reply other threads:[~2021-12-09 16:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 19:51 Achim Gratz
2021-12-02 20:24 ` Marco Atzeri
2021-12-02 20:45 ` Achim Gratz
2021-12-02 21:36 ` Marco Atzeri
2021-12-04 12:33 ` Achim Gratz
2021-12-04 13:02 ` Marco Atzeri
2021-12-02 20:26 ` Ken Brown
2021-12-03 10:22 ` ASSI
2021-12-03 11:59 ` Corinna Vinschen
2021-12-03 13:42 ` ASSI
2021-12-03 16:14 ` [GOLDSTAR] " Corinna Vinschen
2021-12-03 20:40 ` Achim Gratz
2021-12-08 18:46 ` Achim Gratz
2021-12-09 10:24 ` Corinna Vinschen
2021-12-09 16:11 ` Ken Brown [this message]
2021-12-09 18:30 ` Achim Gratz
2021-12-03 20:47 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0cab6c70-e8d1-a10f-94a5-b0eba4b2bb8d@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).