From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: treinen@lri.fr, caml-list@inria.fr
Subject: Re: copyright of byte code containing the run time system
Date: Tue, 26 Sep 2000 11:28:14 +0200 [thread overview]
Message-ID: <20000926112814.40539@pauillac.inria.fr> (raw)
In-Reply-To: <m13b6c2-000TZxC@seneca>; from Ralf Treinen on Mon, Sep 18, 2000 at 09:29:57PM +0200
> Please forgive me if this has already has been discussed. I am confused
> by the new LGPL/Q license of ocaml. The ocaml source distribution
> details the copyright of the different source files, however, I have some
> doubts about the implications for the compiled tools. Here is my
> problem:
>
> I'm building a binary distribution of a program which is itself GPL
> licensed. There are three different ways to build an "executable":
>
> 1.) compiled to native code
> 2.) compiled to byte code, packaged without the runtime system
> (in this case, the user would have to install an ocaml package
> which comes with it own license).
> 3.) compiled to byte code and with the runtime system (compiled with -custom)
Our intent is that you should be able to link with the OCaml libraries
and runtime system, and distribute the resulting executable without
any restrictions. We chose the LGPL for these part of the systems
precisely to allow this.
Now, there is some fine print in the LGPL that makes a subtle
distinction between static linking and dynamic linking, which we did
not understand at first (and we now find this distinction silly and useless).
But even with the most pessimistic reading of the LGPL, there cannot
be any problems if your main program is itself under a free license
such as the GPL or LGPL.
> I understand that in cases (1) and (2) the OCaml license does not impose
> any new constraints on the copyright. In case (3), I plan to add the
> following text to the existing (GPL) license of the software:
>
> The executable code contains a copy of the OCaml runtime system
> which is licensed under the terms of the Gnu Library General
> Public License. [followed by a reference to the LGPL text].
This is more than the LGPL requires. Feel free to add or not to add
this paragraph to the license of your software.
Best regards,
- Xavier Leroy
next prev parent reply other threads:[~2000-09-26 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-18 19:29 Ralf Treinen
2000-09-26 9:28 ` Xavier Leroy [this message]
2000-09-28 9:53 ` Sven LUTHER
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=20000926112814.40539@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=treinen@lri.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