Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Thu, 20 Jul 2000 16:38:06 -0400 Message-Id: <200007202038.QAA32487@envy.delorie.com> From: DJ Delorie To: scarter@emware.com CC: cygwin@sourceware.cygnus.com In-reply-to: <50028CAE26D1D3118C7F00A0CC50D6252D1E49@EMWARESERVER> (message from Scott Carter on Thu, 20 Jul 2000 14:25:29 -0600) Subject: Re: make --win32 incorrectly handles PATH References: <50028CAE26D1D3118C7F00A0CC50D6252D1E49@EMWARESERVER> > d) With my apologies to "FREE" software proponents everywhere, my > company exists to profit from non-free software. No need to apologize. You are free to make whichever choices you wish, just as we are free to choose otherwise. > If, as an employee of a company that sells non-free software, I > modify the make source, then we distribute the cygwin1.dll and > (modified) make.exe binaries, and our customers use that make.exe to > compile our code on their machines, what implications does that have > vis-a-vis the GPL?? Your responsibilities under the GPL are the same whether you changed the binaries or not. If you distribute make.exe and cygwin1.dll, you are required to also distribute the sources used to build them - regardless of whether you changed those sources or not. The act of *using* make/cygwin to do something else (i.e. control build processes) in no way affects the copyright status or distribution terms of those "something else"'s. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com