-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to NightStrike on 8/19/2009 7:38 PM: > Currently, the way that I understand it is that automake has versioned > binaries such that autoreconf will call for instance automake-1.11. > This makes it very easy to have multiple versions installed. > > Will autoconf ever support this? If someone ever submits patches for it. My personal feel is that since 2.60, we have been paying closer attention to maintaining backwards compatibility (or at least documenting which constructs will work across multiple autoconf versions), so there isn't that much of a compelling reason to need multiple versions installed. Historically, the same can't be said (the changes between 2.13, 2.50, and 2.59 have indeed caused some compatibility nightmares). In automake parlance, the autoconf jump from 2.63 to 2.64 would be like going from 1.10 to 1.10.1 to 1.10.2 (which are all numbered as automake-1.10), rather than going from 1.10.2 to 1.11 (where the automake suffix changes). - -- Don't work too hard, make some time for fun as well! Eric Blake ebb9@xxxxxxx -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqOnWoACgkQ84KuGfSFAYAGJgCcDXwkCBgffxXYVSpTHuhf7Rqc C/oAoLRvwyKv2Ka7AtS7OOioPU1SlArW =sghE -----END PGP SIGNATURE----- _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
