From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
To: cygwin-licensing@cygwin.com
Subject: Re: Combining cygwin with non-free portability libraries
Date: Thu, 14 Oct 2004 17:24:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.61.0410141310090.24756@slinky.cs.nyu.edu> (raw)
In-Reply-To: <20041014170547.GB24493@trixie.casa.cgf.cx>
On Thu, 14 Oct 2004, Christopher Faylor wrote:
> On Thu, Oct 14, 2004 at 12:18:47PM -0400, Igor Pechtchanski wrote:
> >Incidentally, while perusing the GPL FAQ, I stumbled upon
> ><http://gnu.org/licenses/gpl-faq.html#MoneyGuzzlerInc>. There seem to be
> >several cases of Cygwin packages that may do something similar (in fact,
> >Cygwin itself technically does that :-D). Are there implications?
>
> If there are Cygwin packages which are bundling libraries that do not
> include source then they shouldn't be in the distribution.
Not bundling. Linking. The libraries *are* obtained separately.
> What packages are you referring to? I'll pull them immediately.
Well, "cygwin", for one. It links with Windows system DLLs, which are
most definitely proprietary. I wasn't trying to point to a particular
package, this was indeed a licensing question -- in what way does the
above FAQ entry apply to Cygwin packages in general?
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"Happiness lies in being privileged to work hard for long hours in doing
whatever you think is worth doing." -- Dr. Jubal Harshaw
next prev parent reply other threads:[~2004-10-14 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 16:18 Combining Cygwin " Igor Pechtchanski
2004-10-14 17:05 ` Combining cygwin " Christopher Faylor
2004-10-14 17:24 ` Igor Pechtchanski [this message]
2004-10-14 17:42 ` Christopher Faylor
2004-10-14 19:37 ` Igor Pechtchanski
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=Pine.GSO.4.61.0410141310090.24756@slinky.cs.nyu.edu \
--to=pechtcha@cs.nyu.edu \
--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).