-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Sebastian Pipping on 12/11/2007 1:13 AM: > While were talking about AC_PREREQ: I thought maybe requiring > version "2.61a" would be a bad idea if an older version like > "2.60" is enough already, especially with an alpha version. You are correct that requiring the oldest version where a feature was added, instead of the bleeding-edge version that you tested with, makes your project somewhat easier to develop on systems that haven't caught up with the latest autotools in their distro. > Is there some place with information for what versions the > API actually changed so I can require the minimum instead? The NEWS file is supposed to be the canonical source for this sort of information, although it is sometimes incomplete. I'm slowly adding it in the documentation for macros that I touch, but that is also incomplete. For a full history of when any feature was added, you'll have to consult the ChangeLog* files. In the meantime, patches to improve NEWS or the documentation are welcome. - -- Don't work too hard, make some time for fun as well! Eric Blake ebb9@xxxxxxx -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHXov384KuGfSFAYARAvl0AJ9rewKEu0lDx3g5edh2EZiFbn5fmwCeI1Sr xpxPkV2HBEN/VovtqicKSEg= =J439 -----END PGP SIGNATURE----- _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
