This is the mail archive of the
gsl-discuss@sources.redhat.com
mailing list for the GSL project.
Re: GPL - GSL and derivative work.
- To: Nicolai Hanssing <nuh at kampsax dot dtu dot dk>
- Subject: Re: GPL - GSL and derivative work.
- From: "Timothy H. Keitt" <tklistaddr at keittlab dot bio dot sunysb dot edu>
- Date: Sun, 08 Jul 2001 13:06:16 -0400
- CC: gsl-discuss at sources dot redhat dot com
- Organization: State University of New York at Stony Brook
- References: <Pine.LNX.4.21.0107081304450.25079-100000@carlsberg.kampsax.dtu.dk>
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 GPL to link with GPL library. In any
case, the copyright holders are free to issue you an alternative license
if they so choose.
T.
Nicolai Hanssing wrote:
>Dear listmembers
>
>I was wondering what the authors of gsl, consideres to be derivative work.
>An example follows:
>
>--------
>A firm writes an application, that uses/links with gsl. The firm does not
>however modify the gsl-source.
>
>Now the firm wants to sell/distribute the application, then what is forced
>by the GPL?
>
>The firm,
>*) Has to make the source of the application publicly available?
>I.e. will rewrite the application to not use GSL .... :-)
>*) Has to distribute the source of gsl along with the application?
>*) Has to include the GPL-license in the documaentation?
>*) Must not advertize with the use of GSL without permission?
>*) anything else...
>
>I'm currently writing my thesis in cooperation with a firm, and I'm using
>gsl, so what are the firm's possibilities afterwards [of course the source
>is public - it's a thesis] for future use?
>
>
>Regards
> Nicolai Hanssing
> Denmark
>
--
Timothy H. Keitt
Department of Ecology and Evolution
State University of New York at Stony Brook
Stony Brook, New York 11794 USA
Phone: 631-632-1101, FAX: 631-632-7626
http://life.bio.sunysb.edu/ee/keitt/