Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 21 Dec 2001 11:39:46 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: GPL Violation - VCDImager Message-ID: <20011221163946.GG13470@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <3C21A41F.1040508@ece.gatech.edu> <3C21A752.9090401@ece.gatech.edu> <20011220104559.H21898@cygbert.vinschen.de> <013c01c1893b$61fc6050$0200a8c0@lifelesswks> <20011220192323.GA3208@redhat.com> <20011220235454.B21898@cygbert.vinschen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.1i On Fri, Dec 21, 2001 at 10:26:46AM +0100, Andrew Markebo wrote: >Isn't a link to cygwin.com enough?? No. What happens if cygwin.com goes away? Then how do people get their source code? You don't rely on other people to satisfy the GPL obligation of providing source code for binaries that you distribute. This is a very common misconception, though. It is so common that it is brought up nearly every single time, I contact someone about a GPL violation. 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/