Just saw this on the Cygwin.Applications mailing list that indicates a potential issue linking a GPLv3 program to a GPLv2 library.
(http://sources.redhat.com/ml/cygwin-apps/2007-07/msg00000.html) ===== GPLv3 * 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----- Hash: SHA1 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 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 iD8DBQFGhyQW84KuGfSFAYARAm1hAJ95tpXEgzvMe4aUNXDdQ3wn0lVt/gCff7fa 73gosNY4OYf3Q43aRe3bMZg= =BeWb -----END PGP SIGNATURE----- ===== -- Soh Kam Yung my Google Reader Shared links: (http://www.google.com/reader/shared/16851815156817689753) my delicious links: (http://del.icio.us/SohKamYung) my simpy links: (http://www.simpy.com/user/kysoh/links) _______________________________________________ Slugnet mailing list [email protected] http://www.lugs.org.sg/mailman/listinfo/slugnet
