public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Justin Guyett <jfg@sonicity.com>
To: Michael Eager <eager@mvista.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: Compiler for Red Hat Linux 8
Date: Wed, 18 Jul 2001 19:26:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.30.0107181911580.20958-100000@straylight.int.sonicity.com> (raw)
In-Reply-To: <3B563EED.D55AB932@mvista.com>

On Wed, 18 Jul 2001, Michael Eager wrote:

> Unless I'm reading the GPL incorrectly, this does not violate the GPL.
>
> GPL does not require that code which depends on NDA info to be made public.
> It says that if you produce a product using GPL code, that the source must be
> made available to the recipient of the product and that the derived product
> must be licensed under the GPL.  It does not mandate that you publicly
> distribute the product nor does it prohibit your distribution of the product
> selectively.

That's not my impression...

Yes, you can close the source and keep it in-house, and you can distribute
it to only 1 other person if that's what you want to do.  However, the GPL
_forces_ you to give GPL rights to anyone you distribute software to,
which conflicts with every NDA I've ever seen.  That one person you give
it to then must be allowed to distribute it, modified or not, to anyone
[s]he wants.  Otherwise it's not GPL'd, and thus you cannot give it to
them.

The GPL doesn't only protect the right of people to get source code to
modified versions they received, but also protects the right of those
people to distribute their copies, modified or not.  Otherwise anyone can
tack on a "you must get permission from us before you redistribute" which
is obviously not allowed.

If redhat is allowed to do this to gcc, microsoft can do the same thing,
wrap it in an "NDA" license, and even if you get the program and request
source (which they then must provide), you can't make changes or
distribute it to others.  Seems like a NDA is clearly incompatible with
the GPL.


justin

  reply	other threads:[~2001-07-18 19:26 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-18 14:41 dewar
2001-07-18 15:29 ` Geoff Keating
2001-07-18 17:50   ` Joe Buck
2001-07-18 18:59 ` Michael Eager
2001-07-18 19:26   ` Justin Guyett [this message]
2001-07-19  9:05     ` Mark Mitchell
2001-07-19 19:28   ` akbar A.
2001-07-18 22:10 ` Per Bothner
2001-07-18 22:19   ` Joe Buck
2001-07-18 22:38     ` Per Bothner
2001-07-18 23:00       ` Alex Rosenberg
2001-07-19 14:05       ` Jonathan Larmour
  -- strict thread matches above, loose matches on Subject: below --
2001-07-19 23:16 Bernard Dautrevaux
2001-07-19 10:49 dewar
2001-07-19  4:33 dewar
2001-07-19  1:36 Bernard Dautrevaux
2001-07-19  2:40 ` Joseph S. Myers
2001-07-19  3:02 ` Roman Zippel
2001-07-19  3:12 ` Russ Allbery
2001-07-19  0:29 Bernard Dautrevaux
2001-07-19  1:16 ` Toon Moene
2001-07-18 20:02 dewar
2001-07-18 14:33 Geoff Keating
2001-07-18 13:21 Benjamin Kosnik
2001-07-17 20:00 Benjamin Kosnik
2001-07-17 17:37 mike stump
2001-07-17 13:04 Geoff Keating
2001-07-17 15:52 ` Joe Buck
2001-07-17 17:48   ` Per Bothner
2001-07-18  8:55     ` Joseph S. Myers
2001-07-17 18:24 ` Craig Rodrigues
2001-07-18  2:41 ` Andreas Jaeger
2001-07-18  9:03   ` H . J . Lu
2001-07-18 12:01     ` Joe Buck
2001-07-18 12:46       ` H . J . Lu
2001-07-18 13:22         ` Joe Buck
2001-07-18 13:31           ` H . J . Lu
2001-07-18 14:28             ` David Edelsohn
2001-07-18 15:03               ` Joern Rennecke
2001-07-18 15:12                 ` David Edelsohn
2001-07-18 15:24                   ` Joe Buck
2001-07-18 17:05                     ` H . J . Lu
2001-07-19  4:56                     ` Toon Moene
2001-07-18 15:41                 ` Joseph S. Myers
2001-07-18 16:23                   ` H . J . Lu
2001-07-18 12:18     ` Sergey Ostrovsky
2001-07-18 15:19       ` Ken Whaley
2001-07-18 15:30         ` Toon Moene
2001-07-18 15:59           ` Ken Whaley
2001-07-18 16:08             ` Toon Moene
2001-07-18 13:30   ` Gerald Pfeifer
2001-07-19  5:17     ` Andreas Jaeger
2001-07-19 12:23       ` Gerald Pfeifer
2001-07-18 19:07   ` LinuxVN
2001-07-18 13:44 ` Toon Moene

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.LNX.4.30.0107181911580.20958-100000@straylight.int.sonicity.com \
    --to=jfg@sonicity.com \
    --cc=eager@mvista.com \
    --cc=gcc@gcc.gnu.org \
    /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).