Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Sven LUTHER <luther@dpt-info.u-strasbg.fr>
To: Xavier Leroy <Xavier.Leroy@inria.fr>
Cc: treinen@lri.fr, caml-list@inria.fr
Subject: Re: copyright of byte code containing the run time system
Date: Thu, 28 Sep 2000 11:53:35 +0200	[thread overview]
Message-ID: <20000928115335.A10844@lambda.u-strasbg.fr> (raw)
In-Reply-To: <20000926112814.40539@pauillac.inria.fr>; from Xavier.Leroy@inria.fr on Tue, Sep 26, 2000 at 11:28:14AM +0200

On Tue, Sep 26, 2000 at 11:28:14AM +0200, Xavier Leroy wrote:
> > 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).

Xavier, ...

why not clarify further this further and simply state in your licence that the
runtime is under the LGPL, with the added permission to distribute statically
linked code. I don't have it under my eyes right now, but i think you
understand the idea.

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

Anyway, the only problem that could arise would be if INRIA (or whoever hold
the copyright for the runtime) decide to begin suing people about it. I don't
think this will happen.

Also, what about the toplevel ?

I guess a program built with ocamlmktop would be under the QPL, since it
contains not only the runtime, but also some part of the compiler needed for
parsing ocaml sentences ?

But then i may be wron, didn't look at the files involved.

Friendly,

Sven LUTHER



      reply	other threads:[~2000-09-28 14:57 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
2000-09-28  9:53   ` Sven LUTHER [this message]

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=20000928115335.A10844@lambda.u-strasbg.fr \
    --to=luther@dpt-info.u-strasbg.fr \
    --cc=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