public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Steve ROBBINS <stever@bic.mni.mcgill.ca>
To: Edwin Robert Tisdale <E.Robert.Tisdale@jpl.nasa.gov>
Cc: gsl-discuss@sources.redhat.com
Subject: Re: GPL - GSL and derivative work.
Date: Wed, 19 Dec 2001 13:20:00 -0000	[thread overview]
Message-ID: <20010814120229.O17986@bottom.bic.mni.mcgill.ca> (raw)
In-Reply-To: <3B793BF6.1C6E2E31@jpl.nasa.gov>

On Tue, Aug 14, 2001 at 07:55:50AM -0700, Edwin Robert Tisdale wrote:
> Timothy H. Keitt wrote:
> 
> > These are pretty clearly spelled out at www.gnu.org.
> > Short answer: LGPL, linking from closed-source OK.;
> > GPL, you have to release the source of the application
> > under the GPL to link with a GPL'd library.
> 
> The GPL only prevents you from distributing the GPL'd library
> without distributing the application source code.
> You can distribute the application object code
> without the application source code without violating the GPL
> and let users link it into the GPL'd library themselves.

This is not true.  If your application requires the GPL'd library
it is to be considered a "derived work" of the library, and all
sources must be shipped with a binary.  This is pretty clearly
laid out in the text of the GPL, and the GNU web site has further
disucssions.  In particular, see

  http://www.gnu.org/licenses/gpl-faq.html#IfLibraryIsGPL


If you intend to split legal hairs about what constitutes
a "derived work", that is a discussion I do not want to have.
Try the newsgroup gnu.misc.discuss.


> I don't think that there is any practical way for the FSF
> or the library developers to prevent users from doing this.

Well, the practicality is a separate question.  ;-)
But it is beyond question that this is not what authors of
GPL'd libraries *intend*.

-Steve

  reply	other threads:[~2001-12-19 13:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 13:20 Edwin Robert Tisdale
2001-12-19 13:20 ` Steve ROBBINS [this message]
2001-12-19 13:20 ` Mark Galassi
  -- strict thread matches above, loose matches on Subject: below --
2001-12-19 13:20 Edwin Robert Tisdale
2001-12-19 13:20 ` Mark Galassi
2001-12-19 13:20 Edwin Robert Tisdale
2001-12-19 13:20 ` Mark Galassi
2001-12-19 13:20 Edwin Robert Tisdale
2001-12-19 13:20 ` Mark Galassi
2001-12-19 13:20 Edwin Robert Tisdale
2001-12-19 13:20 Nelder-Mead Simplex Brian Gough
2001-12-19 13:20 ` GPL - GSL and derivative work Nicolai Hanssing
2001-12-19 13:20   ` Timothy H. Keitt

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=20010814120229.O17986@bottom.bic.mni.mcgill.ca \
    --to=stever@bic.mni.mcgill.ca \
    --cc=E.Robert.Tisdale@jpl.nasa.gov \
    --cc=gsl-discuss@sources.redhat.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).