-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Dalibor Topic on 1/25/2008 9:21 AM: | Ralf Wildenhues <Ralf.Wildenhues <at> gmx.de> writes: | |> I'm pleased to announce the release of Automake 1.10.1. | | I assume that means the GPLv3 exceptions vs. autotools mess has not been | resolved yet, as there is no mention of it in the release notes? Correct - Ralf intentionally downgraded the license on the automake release branch just prior to releasing 1.10.1 [1]. The issue is closer to resolution (the FSF lawyers have finally given the maintainers an off-list preview of what wording might be possible to use), but not there yet. Technically, it would also be possible for autoconf to pull the same trick as automake - downgrade the license of all files in git to GPLv2+, release autoconf 2.62, then upgrade back to GPLv3+ once the licensing is sorted out, but I'd rather avoid that since it looks like the FSF lawyers are finally working on the problem. [1] http://git.sv.gnu.org/gitweb/?p=automake.git;a=commit;h=fd94284 - -- 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 iD8DBQFHmhsT84KuGfSFAYARArXAAJ9TMf2tpn3EKVX3+kKzu72DzX4SGwCeMkwq FyUN3HEL3F3kmqsCtcHF5c8= =Ci6g -----END PGP SIGNATURE----- _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
