caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@users.sourceforge.net>
To: Ville-Pertti Keinonen <will@exomi.com>
Cc: David Brown <caml-list@davidb.org>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Announce: Schoca-0.2.3 released
Date: 26 Oct 2004 00:42:35 +1000	[thread overview]
Message-ID: <1098715355.3075.279.camel@pelican.wigram> (raw)
In-Reply-To: <417CB289.1010700@exomi.com>

On Mon, 2004-10-25 at 18:00, Ville-Pertti Keinonen wrote:

> I really don't know what the legal interpretation of that would be.

I do: creating a compatible component without actually
deriving from GPL sources doesn't breach copyright. In particular,
complying to an interface just by itself cannot breach copyright.

So, for example, a program which was able to accept
readline -- and is able to do so *without* reading any
GPL headers and *without* reading a header derived from
it -- doesn't have to be GPL.

This has nothing to do with what Stallman wants, it's
a universal property of Copyright.

So the code *before* linkage against readline doesn't
need to be GPL. Once linked against readline the result
probably does have to be GPL.

There is actually an example of this: Python. 
The top level interpreter does use readline.
Yet Python sources definitely aren't GPL.

The actual binary, when linked against readline,
probably is. So if you install Python with an RPM,
its a GPL version you have installed. If you use
the tarball the source isn't GPL, but as with the RPM
the binary is.

I don't see that linking statically or dynamically
makes a difference .. except for the amusing situation
that if you actually used dlopen and a shared library,
the licence would change dynamically as you loaded
and unloaded the library . :)))

Oh .. Python doesn't display the GPL licence interactively .. 
even with readline linked in .. (which is probably a breach
of the GPL of readline)

If you have Python installed, type 'license()' in the top
level .. it's quite interesting.

-- 
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850, 
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net




  parent reply	other threads:[~2004-10-25 14:44 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
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           ` skaller [this message]
2004-10-25 15:52           ` [Caml-list] " 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=1098715355.3075.279.camel@pelican.wigram \
    --to=skaller@users.sourceforge.net \
    --cc=caml-list@davidb.org \
    --cc=caml-list@inria.fr \
    --cc=will@exomi.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 NNTP newsgroup(s).