From: Ville-Pertti Keinonen <will@exomi.com>
To: David Brown <caml-list@davidb.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Announce: Schoca-0.2.3 released
Date: Mon, 25 Oct 2004 11:00:09 +0300 [thread overview]
Message-ID: <417CB289.1010700@exomi.com> (raw)
In-Reply-To: <20041025050127.GA3599@old.davidb.org>
David Brown wrote:
>The GPL only coveres distribution, not execution. GPL code can be linked
>with even proprietary code as long as the result isn't distributed at all.
>
>
This is getting fairly offtopic, but I thought it might be worth
mentioning that this is not quite so clear-cut.
While you're essentially correct, the above could also be interpreted to
mean that you can get around the GPL by having the end-user link
GPL-incompatible software against a GPL component. According to RMS,
this is not acceptable, even for a minor, optional component (he
demanded that CLISP change its licensing due to the optional ability to
link against GNU readline; the author changed to GPL).
On the other hand, a similar practice is commonly accepted for Linux
kernel modules.
Consider a situation where someone created a compatible but non-GPL
replacement for some major GPL library, and GPL-incompatible software
that could be linked against that library...or the original GPL
library. Lets say the original GPL library is sufficiently better that
most users link against it.
The above could be extended to turn any GPL program into a library
first, then create a crappy compatible library...
I really don't know what the legal interpretation of that would be.
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-10-25 8:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-24 9:03 Christoph Bauer
2004-10-24 18:29 ` skaller
2004-10-25 2:58 ` David Brown
2004-10-25 3:38 ` Jacques Garrigue
2004-10-25 5:01 ` David Brown
2004-10-25 6:08 ` Jacques Garrigue
2004-10-25 6:40 ` skaller
2004-10-25 8:00 ` Ville-Pertti Keinonen [this message]
2004-10-25 14:35 ` Stefan Monnier
2004-10-25 15:15 ` [Caml-list] " skaller
2004-10-25 15:25 ` Stefan Monnier
2004-10-25 14:42 ` [Caml-list] " skaller
2004-10-25 15:52 ` David Brown
2004-10-25 18:10 ` Hartmann Schaffer
2004-10-25 5:56 ` [Caml-list] licence stuff again skaller
2004-10-25 5:18 ` [Caml-list] Announce: Schoca-0.2.3 released skaller
2004-10-25 5:29 ` David Brown
2004-10-25 6:07 ` skaller
2004-10-27 14:42 ` Sven Luther
2004-10-27 14:40 ` Sven Luther
2004-10-27 16:04 ` skaller
2004-10-27 17:46 ` David Brown
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=417CB289.1010700@exomi.com \
--to=will@exomi.com \
--cc=caml-list@davidb.org \
--cc=caml-list@inria.fr \
/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 NNTP newsgroup(s).