public inbox for cygwin-licensing@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin-licensing@cygwin.com
Subject: Re: Combining cygwin with non-free portability libraries
Date: Thu, 14 Oct 2004 17:42:00 -0000	[thread overview]
Message-ID: <20041014172502.GA24797@trixie.casa.cgf.cx> (raw)
In-Reply-To: <Pine.GSO.4.61.0410141310090.24756@slinky.cs.nyu.edu>

On Thu, Oct 14, 2004 at 01:12:26PM -0400, Igor Pechtchanski wrote:
>>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?

This is basic GPL stuff.  There is no violation of the package is using
system libraries.  Otherwise you couldn't use GPLed packages on HP/UX,
Solaris, Tru64, etc.

"However, as a special exception, the source code distributed need not
include anything that is normally distributed (in either source or
binary form) with the major components (compiler, kernel, and so on) of
the operating system on which the executable runs, unless that component
itself accompanies the executable."

  reply	other threads:[~2004-10-14 17:24 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
2004-10-14 17:42     ` Christopher Faylor [this message]
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=20041014172502.GA24797@trixie.casa.cgf.cx \
    --to=cgf-no-personal-reply-please@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).