From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22508 invoked from network); 8 Feb 2002 03:39:51 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 8 Feb 2002 03:39:51 -0000 Received: (qmail 11664 invoked by alias); 8 Feb 2002 03:39:30 -0000 Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 4664 Received: (qmail 11643 invoked from network); 8 Feb 2002 03:39:28 -0000 Date: Thu, 7 Feb 2002 21:39:11 -0600 From: Dan Nelson To: Christopher Faylor Cc: Andrew Markebo , Gary Oberbrunner , Zefram , Gabor , zsh-users@sunsite.dk Subject: Re: usage of zsh for profit? Message-ID: <20020208033911.GC14616@dan.emsphone.com> References: <20020206104852.A74470@vmunix.com> <20020206160524.GB26831@fysh.org> <3C6176A8.1050600@genarts.com> <20020208004516.GA19351@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020208004516.GA19351@redhat.com> User-Agent: Mutt/1.3.27i X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error In the last episode (Feb 07), Christopher Faylor said: > Note that if you provide the Cygwin DLL, you have to make sources > available for it as well, not just zsh. > > The cygwin buy-out would allow you to not distribute the sources for the > DLL. That means that you'd only have to worry about the ZSH licensing > terms which seem pretty straightforward. > > Again, I am not advocating this. It seems like it should be pretty easy > to just tar up the cygwin sources for whatever you're distributing and > include them somewhere on a CD or, alternately, be ready to provide the > sources if someone asks for them. > > (No, just pointing to the cygwin web site isn't enough to satisfy the GPL) I seem to remember that this IS enough, as long as you're simply building stock zsh with stock cygwin. It's only when you make changes that the "you must make sources available for two years" clause really kicks in. I mean, how many cygwin mirrors do we really need? -- Dan Nelson dnelson@allantgroup.com