Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-Id: <200109110224.f8B2O0Z02552@cate2-108.reshall.ou.edu> To: cygwin AT cygwin DOT com Subject: Re: Virus Found In-Reply-To: Your message of "Mon, 10 Sep 2001 21:17:11 EDT." <20010910211711 DOT A19232 AT redhat DOT com> From: Jon Cast Reply-to: cygwin AT cygwin DOT com Date: Mon, 10 Sep 2001 21:24:00 -0500 Just to set your mind at ease... Christopher Faylor wrote on Mon, 10 Sep 2001 21:17:11 -0400: > Forgive me, if you already know this but you can't use cygwin as the > basis of a commercial application unless you provide the sources for > your apps and for the cygwin DLL, if you are distributing it. Yes I know this. The (planned) apps will be GPLed, and I will ship full source for the entire thing. > Also, if you are distributing the Cygwin DLL or any of its > associated utilities, you also can't just point to the cygwin web > site and say "Get them over there." You must provide the sources > for any software you distribute. You can't rely on Red Hat to > maintain a distribution of the sources. I know this too. Actually, I'm targeting absolute beginners (to *real* programs, anyway), and I don't want them frightened by the commandline nature of the standard Cygwin distribution :) So, I'll mention www.cygwin.com when I mention how to get your binaries, but not before. > The "Licensing Terms" link at the cygwin web site goes into more > details. Great license, btw. Now, if only we could get the FSF to recommend it... Jon Cast p.s. You don't need to Cc: me; I'm suscribed (disregard if this was generated by a perl script or something) -- 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/