From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps <cygwin-apps@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: autoconf-15-1, autoconf2.7-2.71-1
Date: Tue, 7 Dec 2021 15:16:06 -0500 [thread overview]
Message-ID: <a747bb79-eabb-1149-1b44-ba57298eb691@cornell.edu> (raw)
In-Reply-To: <87d575a7-5e48-4320-e6a4-a61b628f71a4@cornell.edu>
[Redirected from the cygwin list,
https://cygwin.com/pipermail/cygwin/2021-December/250149.html]
On 12/7/2021 3:08 PM, Ken Brown wrote:
> On 12/5/2021 3:50 AM, Achim Gratz wrote:
>> Autoconf upstream has stated that the 2.7x releases are not fully
>> backwards compatible. Cygwin therefore chose to provide a new
>> autoconf2.7 package (keeping autoconf2.5 available) and modifying the
>> wrapper script to allow packaging systems to set WANT_AUTOCONF=2.7 to
>> select a newer autoconf version. The default (when no explicit
>> WANT_AUTOCONF is set) is still "2.5", which selects autoconf version
>> 2.69 on Cygwin.
>
> As you explained on IRC earlier today, what you meant is that the default for
> packages built via cygport is still 2.5.
>
>> The default will change to "2.7" after some period of
>> testing.
>>
>> Cygwin package maintainers are encouraged to set WANT_AUTOCONF=2.7 in
>> their cygport configuration or in individual cygport files in order to
>> check for regressions.
I wonder if it would be better to make the default 2.7 in order to more strongly
encourage maintainers to try the latter. They can always set WANT_AUTOCONF=2.5
if they can't make it work. But I would bet that most difficulties that arise
have already been found and fixed by Fedora.
Ken
next parent reply other threads:[~2021-12-07 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <announce.87tufntozm.fsf@Rainer.invalid>
[not found] ` <87d575a7-5e48-4320-e6a4-a61b628f71a4@cornell.edu>
2021-12-07 20:16 ` Ken Brown [this message]
2021-12-08 5:56 ` Brian Inglis
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=a747bb79-eabb-1149-1b44-ba57298eb691@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).