caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: Alex Baretta <alex@barettadeit.com>
Cc: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>,
	sven.luther@wanadoo.fr, caml-list@inria.fr
Subject: Re: [Caml-list] Ocaml license - why not GPL?
Date: Mon, 31 Jan 2005 08:38:14 +0100	[thread overview]
Message-ID: <20050131073813.GC19902@pegasos> (raw)
In-Reply-To: <41FDD853.5090801@barettadeit.com>

On Mon, Jan 31, 2005 at 08:03:47AM +0100, Alex Baretta wrote:
> Jacques Garrigue wrote:
> 
> >To the best of my knowledge, Trolltech decided to release a GPL'ed
> >version of Qt because the QPL is not compatible with the GPL, which is
> >no surprise at all: by definition the GPL is only compatible with
> >itself, or strictly weaker licenses, like BSD or LGPL.
> >
> >This is less of a problem with ocaml, because the part covered by the
> >QPL is the compiler, not the library, so this should only concern
> >persons hacking the compiler itself.
> >
> >Jacques Garrigue
> 
> Hmmm... This is an interesting point! The toplevel library includes the 
> compiler code, which is licensed under the QPL, but yet somehow must be 
> allowed to link to GPLed libraries and programs. If the toplevel library 
>  may not be linked with GPLed code, then the toplevel itself become 
> hardly usable, and a significant portion of my code, which is GPLed and 
> links the toplevel library, would be illegal.

Indeed.

> Might the caml breeders please comment on this issue?

This is an issue mostly ignored right now, where there is no clear will to
solve it, and given the small case of code concerned, nobody bothered.

That said, given the restrictions of the QPL, the GPL compatibility may be
solved by those modification the ocaml team applied  to 3.08.2, or future
modifications.

Another solution is to licence differently the toplevel code.

Friendly,

Sven Luther


  reply	other threads:[~2005-01-31  7:41 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
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 [this message]
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=20050131073813.GC19902@pegasos \
    --to=sven.luther@wanadoo.fr \
    --cc=alex@barettadeit.com \
    --cc=caml-list@inria.fr \
    --cc=garrigue@math.nagoya-u.ac.jp \
    /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).