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 11:39:46 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: GPL Violation - VCDImager Message-ID: <20011221163946.GG13470@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com 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 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/