From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Alex Baretta <alex@barettadeit.com>
Cc: Sven Luther <sven.luther@wanadoo.fr>, Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Ocaml license - why not GPL?
Date: Mon, 31 Jan 2005 10:00:06 +0100 [thread overview]
Message-ID: <20050131090006.GA18352@yquem.inria.fr> (raw)
In-Reply-To: <41FDE282.7040709@barettadeit.com>
> Hmmm... This is an interesting point! The toplevel library includes
> the compiler code, which is licensed under the QPL,
Correct.
> but yet somehow must be allowed to link to GPLed libraries and
> programs.
You meant: "I (Alessandro Baretta) needs to link it to GPLed libraries
and programs". There is no moral imperative of being able to link
something with GPLed stuff.
> If the toplevel library may not be linked with GPLed code,
> then the toplevel itself become hardly usable,
Again, you meant "... usable to me because of my choice of the GPL".
> and a significant
> portion of my code, which is GPLed and links the toplevel library,
> would be illegal.
> Might the caml breeders please comment on this issue?
Only if you stop calling me a "caml breeder". Makes me feel like a
nuclear reactor :-)
More seriously:
- The toplevel library is indeed covered by the QPL.
- Clause 6 of the QPL is pretty clear. In summary, it stipulates that
a QPL-ed library can be linked with pretty much any code that is
distributed as open source. But please don't take my words for it:
read the license.
- The problem in your case is most likely to be with the GPL, which
puts much stronger requirements on any piece of code that comes
in contact with GPL-ed code. But don't take my word for it, as
I have no expertise (and no interest) in license compatibility issues.
Read the GPL, consult license experts, make up your mind.
- If it turns out you have a QPL/GPL incompatibility, you have exactly
three options:
1) don't use the toplevel library
2) put your code under another license than the GPL
3) get a more liberal license for OCaml by becoming a member
of the Caml Consortium.
> This bothers me quite a bit. Am I to expect a legal pursuit from INRIA
> for violating the QPL for having released mixed GPL+QPL code?
No, because you didn't violate our license (the requirements set by
the QPL are met).
> Or am I to pursue myself because the QPL breaks my own GPLed code?
This is more like it :-) You, or your customers. Remember,
inconsistent license = no license = nobody can do anything with your code.
> I would really appreciate an official response from the INRIA people. I
> think Ocaml is a great tool for commercial free software development,
> but in order to be able to build a thriving business I must make sure
> that Xavier et al. won't meet me with a team of Dobermans to settle
> copyright issues...
Again, your problems are not with us. The ones that could come after
you are your customers.
- Xavier Leroy
next prev parent reply other threads:[~2005-01-31 9:00 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
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 [this message]
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=20050131090006.GA18352@yquem.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=alex@barettadeit.com \
--cc=caml-list@inria.fr \
--cc=sven.luther@wanadoo.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