From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: max@sbuilders.com, caml list <caml-list@inria.fr>
Subject: Re: Un point de droit
Date: Mon, 31 Jul 2000 17:30:24 +0200 [thread overview]
Message-ID: <20000731173024.36331@pauillac.inria.fr> (raw)
In-Reply-To: <397F1C55.A38AEB08@sbuilders.com>; from Maxence Guesdon on Wed, Jul 26, 2000 at 07:13:57PM +0200
> a point of law : i developped a tool generating documentation from OCaml
> code ; this tool is linked with some modules of the OCaml distribution.
> What kind of license is needed to make this tool freely available on ze
> net ?
It depends which part of the OCaml distribution you're linking with:
the standard libraries and runtime system (LGPL licence) or the
compiler proper (QPL license).
Assuming for instance that you're linking with some compiler modules,
the QPL asks you to make the source code of your application available
at no charge, and to allow users to redistribute sources or binaries
at no charge either. Any open source license will guarantee this.
Moreover, if you made modifications to some OCaml source files, the
QPL asks that you distribute them "in a form that is separate from
[OCaml]", e.g. as patches. This clause is a bit fuzzy, but a simple,
safe way to comply is to distribute just your own sources (the files
you wrote from scratch, plus diffs for the modified OCaml source files if
any), then instruct users to fetch the OCaml sources and extract the
parts your program needs. The latter can be automated as a Makefile
entry.
For the parts covered by the LGPL, it's harder to see the exact
limitations imposed by the LGPL (it's a long, wordy document), but
everything should be OK if you distribute your application under the
LGPL, the GPL, or any "more free" license (X11, BSD without
advertising clause, etc).
Hope this helps.
- Xavier Leroy
prev parent reply other threads:[~2000-08-02 11:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-26 17:13 Maxence Guesdon
2000-07-31 15:30 ` Xavier Leroy [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=20000731173024.36331@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=max@sbuilders.com \
/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