From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26675 invoked by alias); 2 Jul 2007 18:04:48 -0000 Received: (qmail 26664 invoked by uid 22791); 2 Jul 2007 18:04:47 -0000 X-Spam-Check-By: sourceware.org Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Mon, 02 Jul 2007 18:04:45 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id E01136D47FF; Mon, 2 Jul 2007 20:04:42 +0200 (CEST) Date: Mon, 02 Jul 2007 18:04:00 -0000 From: Corinna Vinschen To: cygwin-apps@cygwin.com Subject: Re: GPLv3 Message-ID: <20070702180442.GE30973@calimero.vinschen.de> Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps@cygwin.com References: <46872417.5010406@byu.net> <468729AE.DFBAD955@dessent.net> <4687B75A.9020700@byu.net> <4687B75A.9020700-PGZyUNKar/Q@public.gmane.org> <20070702073958.GY30973@calimero.vinschen.de> <20070702151834.GC30973@calimero.vinschen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2007-07/txt/msg00012.txt.bz2 On Jul 2 11:28, Andrew Schulman wrote: > > In the meantime, treat the http://cygwin.com/licensing.html page as > > state of the art, especially the open source permission clause. > > Thanks. Ok, I got legal advice now. Linking a GPLv3 application against a GPLv2-only library is not ok because this violates the v2-only license of the library. It does not violate the license of the v3 application. This means, the tar package in the Cygwin distro is not ok (but read on) because it violates Cygwin's license. There's no problem from the tar side, however. There are no short-term plans to change the license of Cygwin, rather we just wait until the OSI certifies the GPLv3 as open source license according to the definitions. As Brian already noted, as soon as the OSI certifies the GPLv3, the exemption clause from http://cygwin.com/licensing.html will also cover GPLv3'ed packages. In the meantime, as long as the GPLv3 is not OSI certified (which shouldn't take long), Red Hat will not enforce the GPLv2-only state of Cygwin on the back of GPLv3 packages. So, tar 1.18 can stay in the distro if Eric trusts Red Hat not to sue him. The same applies to every other maintainer of every other package which goes v3. Actually, cpio goes GPLv3 as well http://lists.gnu.org/archive/html/bug-cpio/2007-06/msg00016.html and as the Cygwin cpio maintainer I will provide the cpio 2.9 release under GPLv3 at any rate since, for some reason, I trust myself not to enforce the GPLv2 on my cpio package ;) I hope that clears the situation sufficiently. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat