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: Wed, 14 Nov 2001 03:33:00 -0000	[thread overview]
Message-ID: <3BF5B765.36282FB7@jpl.nasa.gov> (raw)
Message-ID: <20011114033300.DQuDljU2h5jYNvUrRrX1BBrThV0aX-1W7JiL4_ZOKjI@z> (raw)

Ferdinando Ametrano wrote:

> Once you reimplement GSL, 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.
> quoted from the list archives -- original message by Mark Galassi

Mark Galassi is hardly an authority and he is certainly not impartial.

> Don't you think that
> the message "Can Technical Tricks Circumvent the GPL?"
> by RMS is clear enough?
> If your software *depends* on GPL software, it must be GPL.
> Technical tricks to circumvent this dependency are just that:
> technical tricks.

Nonsense!  Please cite and quote the passage
that supports your assertion that
Anton Fokin cannot distribute his software
without distributing the GSL without it.

Java programmers distribute byte code all the time
which may depend upon a GPL'd Java Virtual Machine (JVM)
which they do not distribute with their code.
You can't force them to release their Java source code
under the terms of the GPL just because it runs in a GPL'd JVM.

             reply	other threads:[~2001-11-17  1:04 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-14  3:33 ` Edwin Robert Tisdale
  -- strict thread matches above, loose matches on Subject: below --
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
     [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-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
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

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=3BF5B765.36282FB7@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).