From: Dan Nelson <dnelson@allantgroup.com>
To: Christopher Faylor <cgf@redhat.com>
Cc: Andrew Markebo <flognat@flognat.myip.org>,
Gary Oberbrunner <garyo@genarts.com>, Zefram <zefram@fysh.org>,
Gabor <gabor@vmunix.com>,
zsh-users@sunsite.dk
Subject: Re: usage of zsh for profit?
Date: Thu, 7 Feb 2002 21:39:11 -0600 [thread overview]
Message-ID: <20020208033911.GC14616@dan.emsphone.com> (raw)
In-Reply-To: <20020208004516.GA19351@redhat.com>
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
next prev parent reply other threads:[~2002-02-08 3:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 15:48 Gabor
2002-02-06 16:05 ` Zefram
2002-02-06 18:32 ` Gary Oberbrunner
2002-02-06 22:13 ` Andrew Markebo
2002-02-08 0:45 ` Christopher Faylor
2002-02-08 3:39 ` Dan Nelson [this message]
2002-02-08 4:03 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020208033911.GC14616@dan.emsphone.com \
--to=dnelson@allantgroup.com \
--cc=cgf@redhat.com \
--cc=flognat@flognat.myip.org \
--cc=gabor@vmunix.com \
--cc=garyo@genarts.com \
--cc=zefram@fysh.org \
--cc=zsh-users@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).