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 Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3E00CF0D.90506@braemarinc.com> Date: Wed, 18 Dec 2002 13:39:57 -0600 From: Gary Van Sickle User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20021217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: cygwin License related Query.... Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit > If you are distributing cygwin1.dll and any of the executables that are > directly associated with it (mount.exe, umount.exe, cygcheck.exe, ps.exe, > kill.exe, cygpath.exe) then you must adhere to the GPL. That means that > you have to make sources available to your customers. > > The fact that you haven't modified the code is irrelevant. The GPL is > about making sure that people who have the binary versions of software > also have access to the source code. We provide both the source code > and the binaries to you. You need to pass that along to your customers, > *unless* you pursue other arrangements with Red Hat. > > Btw, I was trying to move this discussion off of the public list because > it probably isn't of much interest to people there. Well, perhaps, but I think those two paragraphs are the clearest and most concise "layman's terms" explanation of Cygwin licensing I've read to date. All it needs is a "No, a link to the Cygwin site won't cut it" paragraph and I'd say it would make a good FAQ. -- 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/