-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Ralf Wildenhues on 12/4/2007 1:49 PM: > >> I traced it to the fact that I was not using bleeding-edge >> automake. This fixes it, so I'm committing. > > Well, the "fix" would be to release Automake 1.10.1. This is just an > ugly workaround around the licensing holdup. Please let's not go this > way even further.
Any time we depend on automake to supply texinfo.tex as a generated file, and also check in the latest texinfo.tex as copied from the gnulib directory which tracks upstream, you are bound to have mismatch eventually. In other words, it doesn't matter what version of automake we are using (even after 1.10.1 is released); texinfo.tex will eventually change in relation to what the released automake installs. Either texinfo.tex should not be tracked in autoconf's git, or automake should be taught how to grab the latest versions at the time it is invoked (rather than the version as it existed when automake was released), or we teach automake to leave texinfo.tex alone since we maintain it externally (by copying it from gnulib). My patch did the latter option. >> or should we up our minimum requirement to 1.9.6 or 1.10? > > Of course that can still be done. I'm also thinking it might be nice if automake provided a witness macro on whether it supports the dist-lzma option, so that we can write autoconf's configure.ac to conditionally enable dist-lzma if the version of automake is new enough, rather than introducing a hard dependency on (as yet unreleased) automake. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----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 iD8DBQFHVq2684KuGfSFAYARAiK3AJ96aJWssE4T2yedfABG1BC7Njm3pQCghE9V elmVzKRIOQsskXT3k82d5qs= =+uD/ -----END PGP SIGNATURE-----
