Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
To: caml-list@davidb.org
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Announce: Schoca-0.2.3 released
Date: Mon, 25 Oct 2004 12:38:34 +0900 (JST)	[thread overview]
Message-ID: <20041025.123834.26988978.garrigue@math.nagoya-u.ac.jp> (raw)
In-Reply-To: <20041025025832.GA1582@old.davidb.org>

From: David Brown <caml-list@davidb.org>
> On Mon, Oct 25, 2004 at 04:29:59AM +1000, skaller wrote:
> 
> > It would be useful when making an anouncement if you could
> > specify the licence. This saves wasting time. 
> > 
> > On the home page it says:
> > 
> > "This software is free for free software. It is released under the GPL."
> > 
> > Hmm. So if I link it against the Ocaml standard libraries,
> > they have to be GPL'd too. But they're not ..
> 
> What???  I know your distaste for the GPL, but there is no incompatibility
> between the Ocaml standard libraries and a GPL'd program.  The Ocaml
> libraries are LGPL with a special exception that lets you build executibles
> using them, unrestricted.

I was going to make the same answer...

However, when releasing libraries for ocaml, it may be useful to
remember that while ocaml's runtime and libraries are
LGPL(+exception),  the compiler, and as a result the toplevel, is QPL,
and that the QPL happens to be incompatible with the GPL.
In practice, this means that you cannot distribute a toplevel
including a GPL library.

On the other hand, there should be no problem loading manually a
GPL library in the toplevel, or building such a toplevel privately.
(At least I believe so, but questions of dynamic loading are the
muddiest part of the GPL and the QPL.)

Jacques Garrigue

-------------------
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


  reply	other threads:[~2004-10-25  3:38 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 [this message]
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           ` [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=20041025.123834.26988978.garrigue@math.nagoya-u.ac.jp \
    --to=garrigue@math.nagoya-u.ac.jp \
    --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