Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Date: Sun, 18 Feb 2001 12:23:38 -0500
Message-Id: <200102181723.MAA05775@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 <dj AT delorie DOT com>
To: cwilson AT ece DOT gatech DOT edu
CC: robert DOT collins AT itdomain DOT com DOT au, cygwin-apps AT cygwin DOT com
In-reply-to: <3A900513.9467F293@ece.gatech.edu> (cwilson@ece.gatech.edu)
Subject: Re: Wipe out older versions in cygwin/latest, cygwin/contrib
References: <20010217002929 DOT A31035 AT redhat DOT com> <00a501c098a4$885898a0$0200a8c0 AT lifelesswks> <200102181653 DOT LAA05541 AT envy DOT delorie DOT com> <3A900513 DOT 9467F293 AT ece DOT gatech DOT edu>


> When I read this, I went "huh? What about the three-year requirement?" 
> So I went back and re-read the GPL.  In case anyone was wondering, it
> looks like (IANAL) you only have to keep the source code around for
> three years if-and-only-if you initially distributed the binaries
> *without* source availability via the same method.  Your compliance with
> the GPL in that case is predicated on sending a *written* offer with the
> binary that says "Get the sources using such-and-so method".  It is that
> *written* offer which must be valid for three years.
> 
> If you distribute the sources and the binaries at the same time (e.g. as
> is done within cygwin/latest and cygwin/contrib) then you can yank the
> sources whenever you yank the binaries.

Yup.