This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: GPL violations et al

Question (this will lead to my real question, later):

Are the "mirrors" also responsible for providing source for all packages
downloadable by the Cygwin setup.exe?
Most Cygwin packages offer a "Src" tarball available for download along with
the "Bin" package, but there are numerous (significant) exceptions.  For
distributed packages, the source is only available in CVS.  Is the "mirror"
obliged to provide (at minimum) a CVS snapshot (or whatever it might be
(I'm not CVS literate) of the source used for the binary?

This is the real concern for me: while I will willingly provide source for
parts of Cygwin I distribute, I'm not sure were/how to get the *correct
of the source for the binaries I downloaded via setup.exe.


Is it acceptable for setup.exe to allow download of binaries for which the
correct source is not available *from the same source* ?

Thank you,
David Dawson
david. w. dawson@ lmco. com

-----Original Message-----
From: Christopher Faylor [mailto:cgf-gpl at cygwin dot com]
Sent: Tuesday, March 25, 2003 1:38 PM
To: cygwin at cygwin dot com
Subject: Re: GPL violations et al

On Tue, Mar 25, 2003 at 12:54:49PM -0500, Jim Drash wrote:
>A simple reading of the GPL text maks it clear that if you make use of
>GPL software you must provide the same to your "downstream" clients.
>Charles Wilson is correct.
>"Cease and desist" letters are the initial legal step.  However, all
>that needs to be done to avoid any legal action is to put the source on
>the "offending" web site.

Wow.  Could it be said any more clearly than this?

Thank you!


Unsubscribe info:
Bug reporting:

Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]