From: Anton Fokin <anton.fokin@smartquant.com>
To: Ferdinando Ametrano <qf@ametrano.net>
Cc: smartquant@yahoogroups.com,
Brian Gough <bjg@network-theory.co.uk>,
gsl-discuss@sourceware.cygnus.com
Subject: Re: GPL license violation? [GNU Scientific Library]
Date: Wed, 19 Dec 2001 13:20:00 -0000 [thread overview]
Message-ID: <3BF24DB0.D9A17D@smartquant.com> (raw)
Message-ID: <20011219132000.Ns6K4G8Gjn2ZAu5s7adXd0sfa3uUuPLuA5okDlpPSRE@z> (raw)
In-Reply-To: <5.1.0.14.2.20011114103720.00a91ec0@mail.ametrano.net>
Hi guys,
>GSL uses the Gnu Public License (GPL). Therefore, if R-Quant includes GSL
>R-Quant should be GPL-ed too.
Well, R-Quant includes the whole source (actually the whole distribution) of
the GSL. Thus I thought we comply with the requirements. Such distribution is
quite convinient for the end users since they do not need to worry about GSL
download/install.
There are three ways to solve this "problem"
- make a special agreement with GSL/GNU team (such possibility is stated on
GPL pages)
- remove GSL distribution from R-Quant package so that all interested users
can download/install it on
their own. C++ wrappers will still remain.
- remove GSL completely from R-Quant project.
What's your suggestion?
Cheers,
Anton
Ferdinando Ametrano wrote:
> At 10:20 AM 11/14/01 +0100, on the R-Quant mailing list
> ( http://groups.yahoo.com/group/smartquant/message/911 ) Anton Fokin wrote:
> >we have GSL already included in R-Quant distribution.
> >[omissis]
> >I will update R-Quant GSL version to the newest one in the next release.
>
> GSL uses the Gnu Public License (GPL). Therefore, if R-Quant includes GSL
> R-Quant should be GPL-ed too.
> I might be missing some important point here, but I think R-Quant licence
> agreement ( http://www.smartquant.com/license.html ) is not GPL compatible.
>
> Ferdinando Ametrano
next prev parent reply other threads:[~2001-12-19 13:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200111132351.PAA25299@eskimo.com>
[not found] ` <3BF23743.AAEC520D@smartquant.com>
2001-12-19 13:20 ` Ferdinando Ametrano
2001-11-05 5:51 ` Ferdinando Ametrano
2001-12-19 13:20 ` Anton Fokin [this message]
2001-11-06 8:02 ` Anton Fokin
2001-12-19 13:20 ` Kenneth Geisshirt
2001-11-08 2:15 ` Kenneth Geisshirt
2001-12-19 13:20 ` [smartquant] " Anton Fokin
2001-11-08 6:56 ` Anton Fokin
2001-12-19 13:20 ` Anton Fokin
2001-12-19 13:20 ` Brian Gough
2001-11-08 7:03 ` Brian Gough
2001-12-19 13:20 ` Brian Gough
2001-11-08 7:38 ` Brian Gough
2001-12-19 13:20 ` [smartquant] " Anton Fokin
2001-11-09 6:07 ` Anton Fokin
2001-12-19 13:20 ` Brian Gough
2001-11-09 9:19 ` Brian Gough
2001-12-19 13:20 ` Anton Fokin
2001-11-10 2:37 ` Anton Fokin
2001-12-19 13:20 ` Ferdinando Ametrano
2001-11-06 9:53 ` Ferdinando Ametrano
2001-12-19 13:20 ` Anton Fokin
2001-11-07 20:08 ` Anton Fokin
2001-12-19 13:20 ` Ferdinando Ametrano
2001-12-19 13:20 Ferdinando Ametrano
2001-11-06 6:56 ` Ferdinando Ametrano
2001-12-19 13:20 ` Ferdinando Ametrano
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=3BF24DB0.D9A17D@smartquant.com \
--to=anton.fokin@smartquant.com \
--cc=bjg@network-theory.co.uk \
--cc=gsl-discuss@sourceware.cygnus.com \
--cc=qf@ametrano.net \
--cc=smartquant@yahoogroups.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).