This is the mail archive of the
mailing list for the Cygwin project.
- From: Eric Blake <ebb9 at byu dot net>
- To: cygwin-apps <cygwin-apps at cygwin dot com>, cygwin-licensing at cygwin dot com
- Date: Sat, 30 Jun 2007 21:48:39 -0600
- Subject: GPLv3
-----BEGIN PGP SIGNED MESSAGE-----
tar 1.18 was just released, and is one of the first GNU packages that
requires GPLv3 or later. Meanwhile, cygwin is explicit in requiring
exactly GPLv2. According to the GPLv3 FAQ, http://gplv3.fsf.org/dd3-faq,
it is NOT okay for a GPLv3 program to link against a GPLv2-only library.
So, what is the consensus - am I allowed to upload tar 1.18, or is cygwin
forevermore stuck at tar 1.17 as the last GPLv2 release, because of the
fact that building an image of tar 1.18 linked against cygwin1.dll
constitutes a license violation?
And this problem will only grow in the near future - other cygwin packages
that I maintain have discussed in their mailing lists that they are
actively in the process of converting to GPLv3, including findutils
(release expected tomorrow) and m4 (release expected later in the week).
Don't work too hard, make some time for fun as well!
Eric Blake email@example.com
-----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
-----END PGP SIGNATURE-----