From: Chaz Littlejohn <chaz@pokeit.co>
To: cygwin-licensing@cygwin.com
Subject: Re: Bug in Cygwin Windows 8 group permissions
Date: Wed, 05 Dec 2012 09:05:00 -0000 [thread overview]
Message-ID: <CAMgm8F27phkih1dn92zkmmF6WKHgYXUBYdHacUJtitm6jZXwMw@mail.gmail.com> (raw)
In-Reply-To: <CAMgm8F0f1uNyoeE-_SFSQCbOUcK-y9kj3saq0dBC3Rw4jxzL4w@mail.gmail.com>
> On 12/4/2012 4:34 PM, Chaz Littlejohn wrote:
> IANAL but I believe there are 2 issues here:
>
> 1. Whether your use of Cygwin means your program also needs to fall under
> the GPL
>
> 2. Distribution of the Cygwin DLL and its utilities
>
> If what you describe above about your usage of Cygwin is correct, then I
> believe (1) is not an issue for you. However, (2) still applies since you
> cannot distribute GPL'd software without providing the source as well.
I'm not sure if the two are separate. Assuming the program
communicates with cygwin utilities only via command line arguments and
they're not sharing complex data structures, i believe it would be
considered "aggregate" rather than an "modified". From the GPL FAQ
(http://www.gnu.org/licenses/gpl-faq.html#MereAggregation):
"An “aggregate” consists of a number of separate programs, distributed
together on the same CD-ROM or other media. The GPL permits you to
create and distribute an aggregate, even when the licenses of the
other software are non-free or GPL-incompatible. The only condition is
that you cannot release the aggregate under a license that prohibits
users from exercising rights that each program's individual license
would grant them."
Our terms still need to be updated (https://pokeit.co/terms)
It was asked that this conversation be moved to the licensing mailing
list. Previous messages can be found here:
http://cygwin.com/ml/cygwin/2012-12/msg00007.html
http://cygwin.com/ml/cygwin/2012-12/msg00020.html
http://cygwin.com/ml/cygwin/2012-12/msg00024.html
http://cygwin.com/ml/cygwin/2012-12/msg00052.html
http://cygwin.com/ml/cygwin/2012-12/msg00053.html
(IANAL, applies to me as well)
Thanks,
Chaz
next parent reply other threads:[~2012-12-05 9:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMgm8F0K9juGwfGy9DZ=DXMqWNkOk04fR_NUox+fGTwDW56Uug@mail.gmail.com>
[not found] ` <50BE8526.3030602@cygwin.com>
[not found] ` <CAMgm8F0f1uNyoeE-_SFSQCbOUcK-y9kj3saq0dBC3Rw4jxzL4w@mail.gmail.com>
2012-12-05 9:05 ` Chaz Littlejohn [this message]
2012-12-05 9:39 ` Corinna Vinschen
2012-12-06 6:14 ` Chaz Littlejohn
2012-12-06 6:21 ` Christopher Faylor
2012-12-06 8:26 ` Corinna Vinschen
2012-12-06 12:50 ` Chaz
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=CAMgm8F27phkih1dn92zkmmF6WKHgYXUBYdHacUJtitm6jZXwMw@mail.gmail.com \
--to=chaz@pokeit.co \
--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).