From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-licensing@cygwin.com
Subject: Re: Cygwin now licensed under GPLv3+
Date: Thu, 20 Oct 2011 07:49:00 -0000 [thread overview]
Message-ID: <20111020074558.GC18994@calimero.vinschen.de> (raw)
In-Reply-To: <4E9F9CD5.3010203@cisra.canon.com.au>
On Oct 20 15:00, Luke Kendall wrote:
> I wonder if perhaps you have a very precise understanding of what is
> meant by "cygwin" in `Red Hat has relicensed Cygwin from "GNU Public
> License version 2" (GPLv2) to"GNU Public License version 3 or later"
> (GPLv3+)', whereas my (probably wrong) interpretation of "cygwin" is
> "the stuff you can install by Cygwin's setup.exe".
"cygwin" is basically the "cygwin" package, or better, the code in the
source package which comes under the "winsup/cygserver", "winsup/cygwin",
"winsup/lsaauth", and "winsup/utils" directory, except for the source
files which are explicitely given another license (mostly BSD).
The files installed from the "cygwin" binary package are covered by this.
> I say that because I looked in my old Cygwin install ("find c:/ d:/
> -type d -name winsup -print") for a winsup directory but couldn't
> find it, and then fetched the latest cygwin-1.7.9-1.tar.bz2 and
> looked inside that for a winsup directory but again couldn't find a
> directory called anything like "winsup".
See the source package.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
next prev parent reply other threads:[~2011-10-20 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 7:35 Luke Kendall
2011-10-20 7:49 ` Corinna Vinschen [this message]
[not found] <20110419171444.GF23804@calimero.vinschen.de>
2011-09-13 4:44 ` Luke Kendall
2011-09-13 4:58 ` Christopher Faylor
2011-09-13 15:28 ` Luke Kendall
2011-09-13 15:38 ` 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=20111020074558.GC18994@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-licensing@cygwin.com \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).