autoconf-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: plans?


From: Paolo Bonzini
Subject: Re: plans?
Date: Tue, 31 Aug 2010 12:22:17 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.10) Gecko/20100621 Fedora/3.0.5-1.fc13 Lightning/1.0b2pre Mnenhy/0.8.3 Thunderbird/3.0.5

On 08/26/2010 08:03 PM, Ralf Wildenhues wrote:
do you intend to release 2.68 soon, so that GNOME packages (with URLs in
AC_INIT's BUG-ADDRESS) can build again?

If not, I'd like to ping the atomic config.cache and the long lines in
testsuite patches.  Actually, I might want to ping them regardless,
since more intrusive changes are going in ATM anyway.

I think this is a problem with the current release mode of Autoconf. Since 2.64 there has been no release without a serious regression:

** The macro AC_LANG_COMPILER no longer fails on embedded systems that
   lack fopen in the C library, such as AVR or RTEMS (regression
   introduced in 2.64).

** The following undocumented autoconf macros, removed in Autoconf 2.64,
   have been reinstated:
   AH_CHECK_HEADERS

** The macros AC_TYPE_INT8_T, AC_TYPE_INT16_T, AC_TYPE_INT32_T, and
   AC_TYPE_INT64_T work again.  Regression introduced in 2.65.

** AC_CONFIG_SUBDIRS with more than one subdirectory at a time works
   again.  Regression introduced in 2.66.

** AC_CHECK_SIZEOF of a pointer type works again.  Regression
   introduced in 2.66.

** AC_INIT again allows URLs with '?' for its BUG-REPORT argument.
   Regression introduced in 2.66 [and present in 2.67].

Guys, Autoconf cannot afford this. Miss the boat for a widespread Linux distro, and you risk buggy scripts in the wild for years literally.

We _really_, _really_ need a stable branch of Autoconf where every regression is treated the same way as security problems and released in a matter of days. And where only regressions are fixed using the _least invasive_ approach.

Paolo



reply via email to

[Prev in Thread] Current Thread [Next in Thread]