public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Edwin Robert Tisdale <E.Robert.Tisdale@jpl.nasa.gov>
To: gsl-discuss@sources.redhat.com
Subject: Re: [smartquant] Re: GPL license violation? [GNU Scientific Library]
Date: Tue, 13 Nov 2001 08:44:00 -0000	[thread overview]
Message-ID: <3BF54A11.AD3384E0@jpl.nasa.gov> (raw)
Message-ID: <20011113084400.LGioWJA8l7_Cas_PLDK_6yBKYOL9S_6NYxN-neydU0s@z> (raw)

Brian Gough wrote:

> Edwin Robert Tisdale writes:
>
> > Anton may distribute his software without the GSL
> > so that customers would be obliged to obtain the GSL
> > (or another library using the same API) separately
> > and link them together themselves.
>
> I don't think any lawyer
> is going to recommend that as a business model..

Lawyers don't recommend any business model.
They advise their clients on the law.

> Attempting to circumvent a license is illegal too.

I think that you are reading too much into the GPL.

Anton Fokin doesn't need to comply with the GPL
if he doesn't distribute the GSL with his program.
His customers can obtain the GSL from another source
and link it into his code themselves as long as
they don't distribute the GSL with Anton's program.
There is nothing in the GPL or copyright law
that would prevent them from doing so.
It was never the intent of the GPL
to prevent them from doing so.
Your lawyers would advise you that
you would be foolish to sue anybody that did so.
Threatening to do so will not win any friends for the GSL.

I have advised and still advise people to avoid the GSL.
Using the GSL under the GPL simply invites
the copyright holder, the author or any of their customers
to sue them even if they comply with the terms of the GPL.

Please, Brian, if you want people to use the GSL,
try to be a little more helpful and a little less confrontational.



             reply	other threads:[~2001-11-16 17:18 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 13:20 Edwin Robert Tisdale [this message]
2001-11-13  8:44 ` Edwin Robert Tisdale
2001-12-19 13:20 ` José Miguel Buenaposada
2001-11-13  9:24   ` José Miguel Buenaposada
2001-12-19 13:20   ` José Miguel Buenaposada
2001-12-19 13:20 ` Ferdinando Ametrano
2001-11-14  2:36   ` Ferdinando Ametrano
2001-12-19 13:20   ` Ferdinando Ametrano
  -- strict thread matches above, loose matches on Subject: below --
2001-12-19 13:20 Edwin Robert Tisdale
2001-11-14  3:33 ` Edwin Robert Tisdale
     [not found] <200111132351.PAA25299@eskimo.com>
2001-12-19 13:20 ` Ferdinando Ametrano
2001-12-19 13:20   ` Anton Fokin
2001-12-19 13:20     ` Brian Gough
2001-12-19 13:20       ` 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 Edwin Robert Tisdale
2001-11-11  7:20 ` Edwin Robert Tisdale
2001-12-19 13:20 ` Brian Gough
2001-11-12  2:00   ` Brian Gough
2001-12-19 13:20 Edwin Robert Tisdale
2001-11-14  2:37 ` Edwin Robert Tisdale
2001-12-19 13:20 ` Ferdinando Ametrano
2001-11-14  3:04   ` Ferdinando Ametrano
2001-12-19 13:20   ` Dirk Eddelbuettel
2001-11-14  3:21     ` Dirk Eddelbuettel
2001-12-19 13:20     ` Dirk Eddelbuettel
2001-12-19 13:20 Kenneth Geisshirt
2001-12-19 13:20 ` [smartquant] " Anton Fokin
2001-11-08  6:56   ` Anton Fokin

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=3BF54A11.AD3384E0@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).