Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Mon, 23 Apr 2001 00:30:10 -0400 Message-Id: <200104230430.AAA21565@envy.delorie.com> X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f From: DJ Delorie To: Jason DOT Tishler AT dothill DOT com CC: cygwin AT sources DOT redhat DOT com, tim DOT one AT home DOT com, cce AT clarkevans DOT com In-reply-to: <20010423002816.C431@dothill.com> (message from Jason Tishler on Mon, 23 Apr 2001 00:28:16 -0400) Subject: Re: Cygwin Python Distribution GPL Licensing Issue? References: <200104220222 DOT WAA02215 AT envy DOT delorie DOT com> <20010423002816 DOT C431 AT dothill DOT com> The GPL talks about works, not executables. It doesn't matter if readline.dll is a separate file, it's still part of the same work - maybe. IMHO, the test is this: delete readline.dll and run python. Does it run? Does it function normally? If so, readline.dll isn't part of the work. If not, it's all one work, regardless of how many files it is. If they're separate, the mere aggregation of python.exe and readline.dll in the same media (a tarball in this case) is acceptable regardless of licenses. One of the side effects of the cygwin exception is that it implies that linking with libcygwin.a does not cause cygwin1.dll to become part of the work (from our point of view, and for the purpose of interpreting Cygwin's license). Otherwise you'd have the same problem with Cygwin. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple