public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Mark Galassi <rosalia@galassi.org>
To: 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: <8766bhqswf.fsf@galassi.org> (raw)
In-Reply-To: <3B8276DD.75B9C04F@jpl.nasa.gov>

    >> On this list, I simply want to assure anyone that if your
    >> software can only work with GSL then your software is subject
    >> to the relevant parts of the GPL.

    Edwin> The GPL applies only if you distribute your software any
    Edwin> only if you distribute the GPL'd library (GSL) with it.

Of course: I said that you are subject to the relevant parts of the
GPL, so it only applies if you distribute your software.

    Edwin> You cannot copyright the GSL API.  Anybody can implement
    Edwin> the GSL API.

Of course, and once you reimplement GSL then you can say that the
software does not depend on GSL for its functioning.

But until you do, if you distribute software and say "this will only
work with GSL because no other implementation of that API exists" then
you have a derivative work.

  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 ` Mark Galassi [this message]
  -- 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 ` Steve ROBBINS
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
2001-12-19 13:20 Edwin Robert Tisdale

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=8766bhqswf.fsf@galassi.org \
    --to=rosalia@galassi.org \
    --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).