This is the mail archive of the
mailing list for the Cygwin project.
- From: Brian Dessent <brian at dessent dot net>
- To: Eric Blake <ebb9 at byu dot net>
- Cc: cygwin-apps <cygwin-apps at cygwin dot com>, cygwin-licensing at cygwin dot com
- Date: Sat, 30 Jun 2007 21:12:30 -0700
- Subject: Re: GPLv3
- References: <firstname.lastname@example.org>
- Reply-to: cygwin-licensing at cygwin dot com
Eric Blake wrote:
> 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?
Remember that the Cygwin license includes an OSI exemption, so as long
as GPLv3 is eventually OSI certified (as if...) it's fine on the Cygwin
side. I don't know about the other direction though.