From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26389 invoked by alias); 2 Jul 2007 07:40:05 -0000 Received: (qmail 26379 invoked by uid 22791); 2 Jul 2007 07:40:04 -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 07:40:01 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id BE5396D47FF; Mon, 2 Jul 2007 09:39:58 +0200 (CEST) Date: Mon, 02 Jul 2007 07:40:00 -0000 From: Corinna Vinschen To: cygwin-apps Subject: Re: GPLv3 Message-ID: <20070702073958.GY30973@calimero.vinschen.de> Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps References: <46872417.5010406@byu.net> <468729AE.DFBAD955@dessent.net> <4687B75A.9020700@byu.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4687B75A.9020700@byu.net> 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/msg00004.txt.bz2 On Jul 1 08:16, Eric Blake wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > According to Brian Dessent on 6/30/2007 10:12 PM: > >> 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. > > Thanks for the reminder about the exception clause. Since packaging tar > 1.18 does not modify the sources to cygwin1.dll, I agree that the GPLv2 > exception offered by cygwin is applicable here. I don't think GPLv3 will > have any problem achieving OSI exemption, so I went ahead and uploaded tar > 1.18. It's still an interesting point since the GPLv3 linked against a GPLv2 lib with excemption. I'll try to get legal advice about Cygwin and the GPLv3. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat