* Re: [ANNOUNCEMENT] Updated: autoconf-15-1, autoconf2.7-2.71-1
[not found] ` <87d575a7-5e48-4320-e6a4-a61b628f71a4@cornell.edu>
@ 2021-12-07 20:16 ` Ken Brown
2021-12-08 5:56 ` Brian Inglis
0 siblings, 1 reply; 2+ messages in thread
From: Ken Brown @ 2021-12-07 20:16 UTC (permalink / raw)
To: cygwin-apps
[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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [ANNOUNCEMENT] Updated: autoconf-15-1, autoconf2.7-2.71-1
2021-12-07 20:16 ` [ANNOUNCEMENT] Updated: autoconf-15-1, autoconf2.7-2.71-1 Ken Brown
@ 2021-12-08 5:56 ` Brian Inglis
0 siblings, 0 replies; 2+ messages in thread
From: Brian Inglis @ 2021-12-08 5:56 UTC (permalink / raw)
To: cygwin-apps
On 2021-12-07 13:16, Ken Brown wrote:
> [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.
Does Fedora build Windows exes?
Do most packages use libtool?
Remember gnulib? ;^>
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-12-08 5:56 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <announce.87tufntozm.fsf@Rainer.invalid>
[not found] ` <87d575a7-5e48-4320-e6a4-a61b628f71a4@cornell.edu>
2021-12-07 20:16 ` [ANNOUNCEMENT] Updated: autoconf-15-1, autoconf2.7-2.71-1 Ken Brown
2021-12-08 5:56 ` Brian Inglis
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).