From: Edwin Robert Tisdale <E.Robert.Tisdale@jpl.nasa.gov>
To: gsl-discuss@sources.redhat.com
Subject: Re: License
Date: Wed, 19 Dec 2001 13:20:00 -0000 [thread overview]
Message-ID: <3C0BCB45.B46B3F35@jpl.nasa.gov> (raw)
nbecker wrote:
> Suppose I convert part of GSL to C++ templates.
> Now I distribute the modified headers.
> There is no binary distribution of code.
> How does the GPL apply?
If you use any of the code from the original GSL
you must release your code under the terms of the GPL.
If you re-implement the GSL from scratch,
you can release it under any terms you wish.
You must implement the GSL API faithfully
if you are going to call your implementation GSL.
If you deviate from the GSL API,
you should call your library something else besides GSL.
WARNING: multiple messages have this Message-ID
From: Edwin Robert Tisdale <E.Robert.Tisdale@jpl.nasa.gov>
To: gsl-discuss@sources.redhat.com
Subject: Re: License
Date: Wed, 28 Nov 2001 12:16:00 -0000 [thread overview]
Message-ID: <3C0BCB45.B46B3F35@jpl.nasa.gov> (raw)
Message-ID: <20011128121600.9N7k5tTgYKQECCP1WLa6kfY8BnJF4i_0iPloJW0gGrs@z> (raw)
nbecker wrote:
> Suppose I convert part of GSL to C++ templates.
> Now I distribute the modified headers.
> There is no binary distribution of code.
> How does the GPL apply?
If you use any of the code from the original GSL
you must release your code under the terms of the GPL.
If you re-implement the GSL from scratch,
you can release it under any terms you wish.
You must implement the GSL API faithfully
if you are going to call your implementation GSL.
If you deviate from the GSL API,
you should call your library something else besides GSL.
next reply other threads:[~2001-12-19 13:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 13:20 Edwin Robert Tisdale [this message]
2001-11-28 12:16 ` License Edwin Robert Tisdale
-- strict thread matches above, loose matches on Subject: below --
2001-12-19 13:20 License nbecker
2001-11-28 4:37 ` License nbecker
2001-12-19 13:20 ` License Fabrice Rossi
2001-11-28 12:12 ` License Fabrice Rossi
2001-12-19 13:20 ` License Fabrice Rossi
2001-12-19 13:20 ` License Martin Quinson
2001-11-28 11:59 ` License Martin Quinson
2001-12-19 13:20 ` License Brian Gough
2001-11-29 11:15 ` License Brian Gough
2001-12-19 13:20 ` License Brian Gough
2001-11-29 1:44 ` License Brian Gough
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=3C0BCB45.B46B3F35@jpl.nasa.gov \
--to=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).