Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Sat, 9 Feb 2002 13:43:56 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin redistribution and gpl requirements
Message-ID: <20020209184356.GO25500@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <D56B01B8EAA2F0448C873830CB77230E078F68 AT rearadmiral DOT logistics DOT int> <3C642AB3 DOT EDB3D123 AT lapo DOT it>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3C642AB3.EDB3D123@lapo.it>
User-Agent: Mutt/1.3.23.1i

On Fri, Feb 08, 2002 at 08:44:51PM +0100, Lapo Luchini wrote:
>> 1. Include a copy of the GPL with the programs.
>> 2. Reference source code availability at http://cygwin.com
>> Is this sufficient?
>
>You should also have a copy of the source of the distributed version on your
>website (maybe next year you will be using grep version 1.0-1 while cygwin.com
>will only contain a copy of 2.3-1 and 2.3-2).

It doesn't necessarily have to be on your website.  If you release a CD with
the binaries + sources, you're covered.

You basically just can't rely on anyone else to provide the sources for you.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/