caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
To: zyzstar@uid0.sk
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Ocaml license - why not GPL?
Date: Sat, 29 Jan 2005 15:05:38 +0900 (JST)	[thread overview]
Message-ID: <20050129.150538.78035843.garrigue@math.nagoya-u.ac.jp> (raw)
In-Reply-To: <20050128164744.GG13718@osiris.uid0.sk>

From: Jozef Kosoru <zyzstar@uid0.sk>

> I would like to ask O'Caml developers why they have chosen QPL license
> for the compiler and GPL for libraries?
> 
> Of course they have a full right to choose a license they want but I
> think that GPL for the compiler and LGPL for the libraries would be a
> much better choice.

Actually, this is already LGPL (with an exception to make it even more
liberal!) for the runtime and the libraries.
So your only problem with the QPL would be if you need to modify the
compiler itself, and are not happy with the conditions of the QPL.

> Now it is for example impossible to distribute an O'Caml package as a
> part of some O'Caml GPL project source package. Users have to know that
> this program is written in some unusual programming language and they 
> have to download and compile the O'Campl compiler first. For them it
> would be much better to just download the application sources and type
> /configure; make; make install
> .and build process would compile the ocaml compiler (if it's not already
> present) and then compile application sources and install native
> executable (just like C/C++ apps).

The QPL is an official open-source license.
There is nothing preventing you to include the compiler in your
package, as long as you make it clear that the compiler itself is
copyrighted and under the QPL.
(One question is whether you need to include all the tools and
libraries from the distribution, as the QPL seems to imply. I believe
this can be clarified with the developpers if needed.)

So I don't really see your problem...

Jacques Garrigue


  parent reply	other threads:[~2005-01-29  6:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-28 16:47 Jozef Kosoru
2005-01-28 17:08 ` [Caml-list] " David Brown
2005-01-28 19:09   ` Jon Harrop
2005-01-29 23:46     ` Stefan Monnier
2005-01-28 17:14 ` [Caml-list] " Luc Maranget
2005-01-29  6:05 ` Jacques Garrigue [this message]
2005-01-30  6:22   ` Sven Luther
2005-01-31  0:57     ` Jacques Garrigue
2005-01-31  7:03       ` Alex Baretta
2005-01-31  7:38         ` Sven Luther
2005-01-31  7:47           ` Alex Baretta
2005-01-31  7:59             ` Sven Luther
2005-01-31  9:09               ` skaller
2005-01-31  9:23                 ` Sven Luther
2005-01-31  9:00             ` Xavier Leroy
2005-01-31  9:15               ` Sven Luther
2005-01-31  9:47               ` Nicolas Cannasse
2005-01-31 10:29                 ` Xavier Leroy
2005-01-31 10:41                   ` Nicolas Cannasse
2005-01-31 11:08                 ` Alex Baretta
2005-01-31 11:49                   ` Alex Baretta
2005-01-31  7:35       ` Sven Luther
2005-01-30  6:18 ` 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=20050129.150538.78035843.garrigue@math.nagoya-u.ac.jp \
    --to=garrigue@math.nagoya-u.ac.jp \
    --cc=caml-list@inria.fr \
    --cc=zyzstar@uid0.sk \
    /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).