Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Sven LUTHER <luther@maxime.u-strasbg.fr>
To: Xavier Leroy <Xavier.Leroy@inria.fr>,
	Markus Mottl <mottl@miss.wu-wien.ac.at>,
	OCAML <caml-list@inria.fr>
Subject: Re: licence issues
Date: Mon, 19 Apr 1999 15:22:51 +0200	[thread overview]
Message-ID: <19990419152251.A9470@maxime.u-strasbg.fr> (raw)
In-Reply-To: <19990416184022.60993@pauillac.inria.fr>; from Xavier Leroy on Fri, Apr 16, 1999 at 06:40:22PM +0200

On Fri, Apr 16, 1999 at 06:40:22PM +0200, Xavier Leroy wrote:
> It should be pointed out that the current license has (as far as I
> know) never prevented any reasonable use of OCaml.  As a case in point,
> Debian has an OCaml binary package because they didn't have to modify
> anything in the source to make their package.  Similarly, the license
> didn't hamper the development of OLabl, which is clearly a derivative
> work.  Finally, INRIA has never refused any requests for license
> exemptions that have been submitted in the past, and there are no
> indications that this will change in the future.

As the debian maintainer, i just want to add that altough there is a ocaml
debian package, it is in the non-free part of debian, which some may not
consider as being part of debian.

> 
> > It would be a real pity if people ran away /
> > didn't look at OCAML due to some unclear licencing issues.
> 
> It's hard to please everyone.  The GPL makes some other people run
> away (mostly industrial users who don't want to release the source for
> their modifications).  My hope is that while the current license might
> drive away a few license ayatollahs, it should not be an obstacle to 
> all other OCaml users.
> 

What i think you are missing is that with the current license, i don't think
ocaml will be used as a key component of debian, or other free OS, and it is a
shame, especially the bytecode compiler and the VM, would be a nice way of
doing things only one time for all supported architectures, and particularly in
this days where the java virtual machine is presenting some problems with
linux, this could be a good thing for ocaml to become more widely accepted.

But then i also understand your position, and am sure that some middle way
could be reached,

Friendly,

Sven LUTHER




  parent reply	other threads:[~1999-04-19 17:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-16  9:54 Markus Mottl
1999-04-16 16:40 ` Xavier Leroy
1999-04-19 11:56   ` William Chesters
1999-04-20  8:23     ` Xavier Leroy
1999-04-21 19:16       ` Brian Rogoff
1999-04-21 20:08         ` Xavier Leroy
1999-04-21 21:12           ` Brian Rogoff
1999-04-23  9:29           ` Sven LUTHER
1999-04-22  6:40       ` Sven LUTHER
1999-04-19 13:22   ` Sven LUTHER [this message]
1999-04-16 16:41 ` Brian Rogoff
1999-04-19 11:55   ` Michel Mauny
1999-04-19 17:53   ` Pierre Weis
1999-04-20  9:24     ` Dave Berry
1999-04-22  6:43       ` Sven LUTHER
1999-04-22  9:20         ` Dave Berry
1999-04-21  9:38     ` 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=19990419152251.A9470@maxime.u-strasbg.fr \
    --to=luther@maxime.u-strasbg.fr \
    --cc=Xavier.Leroy@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=luther@dpt-info.u-strasbg.fr \
    --cc=mottl@miss.wu-wien.ac.at \
    /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