-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Ralf Wildenhues on 9/8/2009 11:32 PM: > There was no discussion regarding the second Autoconf license exception > RFC. So, OK to commit (if distcheck passes)?
One thing to fix first, but after that, I'm okay with pushing the patch. > I noted that some external files in build-aux also use the old wording > together with v3; that should be fixed in gnulib/texinfo. Can you ping the upstream owners of those files? > The only remaining GPLv2+ files are the perl files synced from Automake > now. (But if you 'mv COPYINGv3 COPYING' after that is sorted out, > remember to adjust Makefile.am and the notices in lib/*/*.m4) Yes, that is a good followup patch, but should not be part of this one. > @@ -70,8 +68,7 @@ General help using GNU software: > <http://www.gnu.org/gethelp/>."] > version=["\ > autoconf (@PACKAGE_NAME@) @VERSION@ > Copyright (C) @RELEASE_YEAR@ Free Software Foundation, Inc. > -License GPLv2+: GNU GPL version 2 or later > -<http://gnu.org/licenses/old-licenses/gpl-2.0.html> > +License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> Per the GNU Coding Standards, http://www.gnu.org/software/automake/manual/standards.html#g_t_002d_002dversion, I would feel more comfortable seeing all the program's --version output include: License GPLv3+/Autoconf: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>, <http://gnu.org/licenses/exceptions.html> (those two URLs fit in one 80-columns row, even if the email wrapped) Or, if we know what URL the Autoconf exception will be given, even calling out that particular page. - -- Don't work too hard, make some time for fun as well! Eric Blake [email protected] -----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/ iEYEARECAAYFAkqnpoIACgkQ84KuGfSFAYCQiQCfR2z0pJ4cz7c8YNx/fhcwdPIT hKYAn3TuldQKbjMrucmx5L5d01XkBauB =aYOR -----END PGP SIGNATURE-----
