Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 21 Dec 2001 10:50:39 +0100 From: Corinna Vinschen To: cygwin Subject: Re: GPL Violation - VCDImager Message-ID: <20011221105039.K21898@cygbert.vinschen.de> Mail-Followup-To: cygwin References: <3C21A41F DOT 1040508 AT ece DOT gatech DOT edu> <3C21A752 DOT 9090401 AT ece DOT gatech DOT edu> <20011220104559 DOT H21898 AT cygbert DOT vinschen DOT de> <013c01c1893b$61fc6050$0200a8c0 AT lifelesswks> <20011220192323 DOT GA3208 AT redhat DOT com> <20011220235454 DOT B21898 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from flognat@flognat.myip.org on Fri, Dec 21, 2001 at 10:26:46AM +0100 On Fri, Dec 21, 2001 at 10:26:46AM +0100, Andrew Markebo wrote: > Isn't a link to cygwin.com enough?? Not much mentioned around it, but > I saw it on the html-pages :-) Ahh under platforms.. No, it's not enough. The license is clear. If you provide a binary Cygwin you'll have to provide the sources for that exact version on your distribution medium, too. If somebody packages something up with a binary Cygwin 1.1.8, where should the user get the sources for that version? Not on our web or ftp pages, at least. That's the reason the sources have to be packed up, too. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/