caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Michael Welsh Duggan <md5i@cs.cmu.edu>
To: Caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] License Conditions for OCaml
Date: Fri, 09 Nov 2001 00:50:22 -0500	[thread overview]
Message-ID: <v1tlmhgpk69.fsf@cs.cmu.edu> (raw)
In-Reply-To: <20011108232434.Y73712-100000@fledge.watson.org> (Patrick M Doane's message of "Thu, 8 Nov 2001 23:30:56 -0500 (EST)")

Patrick M Doane <patrick@watson.org> writes:

> Earlier this year there was a discussion about the problems of using LGPL
> for the OCaml run-time system and associated libraries.
>
> It was suggested that some of the constraints in the LGPL were not
> intended. To quote a page from the Caml website:
>
>   "The LGPL puts no restrictions at all on programs linked with LGPL-ed
> libraries. Thus, users are free to distribute (or not) OCaml-generated
> binaries under whatever conditions they like."
>
> From my reading of the LGPL, which seems to correspond with the
> opinions of others on the list, this just isn't true.

I agree.  The LGPL does put some conditions on the binaries.
For example, they must be accompanied by a copy of the LGPL license.
But this license is *for the Ocaml libraries linked in*, not for the
whole binary.

> If I develop an application with OCaml, I must distribute that
> application with source code.  This isn't acceptable for commercial
> development and I'd really hope that the intention is for OCaml to
> be used outside of academia.

I suggest you read section 6 of the LGPL a little more closely.  I
have to be able to produce on demand source code for ocaml and its
libraries, but not for the work itself.  I do have to distribute the
work in such a way that ocaml and its libraries could change and be
relinked.  

"For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it."

It should be sufficent to distibute all the precompiled *.cm* files
of the binary in the distribution.  These could be linked with a
modified set of ocaml libraries to create a new program, but the
source to the application need not be shipped.

-- 
Michael Duggan
(md5i@cs.cmu.edu)
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


  parent reply	other threads:[~2001-11-09  5:50 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-09  4:30 Patrick M Doane
2001-11-09  4:48 ` Rafael 'Dido' Sevilla
2001-11-09  8:45   ` Xavier Leroy
2001-11-09 15:52     ` Dave Scott
2001-11-09 16:40     ` David Brown
2001-11-09 16:40     ` Brian Rogoff
2001-11-12  8:07       ` Tom
2001-11-12 15:58         ` David Brown
2001-11-09  4:49 ` Will Benton
2001-11-09  5:35   ` Patrick M Doane
2001-11-09  5:53     ` Michael Welsh Duggan
2001-11-09  5:58       ` Patrick M Doane
2001-11-09  9:27         ` Sven
2001-11-09  9:58           ` Julian Assange
2001-11-09 10:37             ` Sven
2001-11-09 15:39             ` Patrick M Doane
2001-11-09 15:36           ` Patrick M Doane
2001-11-09  9:25     ` Sven
2001-11-09 15:33       ` Patrick M Doane
2001-11-09 16:26         ` Tom
2001-11-11 12:25         ` Sven
2001-11-09 11:09     ` malc
2001-11-09 14:46       ` [Caml-list] ELF i386 dynamic linking patch. was: " Jeff Henrikson
2001-11-10  0:32         ` [Caml-list] " malc
2001-11-09  5:50 ` Michael Welsh Duggan [this message]
2001-11-09  8:59 ` [Caml-list] " Sven
2001-11-09 15:13   ` Patrick M Doane
2001-11-11 12:00     ` Sven
2001-11-11 14:56       ` Patrick M Doane
2001-11-26 16:21     ` Fergus Henderson
2001-11-26 16:47       ` Patrick M Doane
2001-11-27 10:28         ` Fergus Henderson
2001-11-27 10:58           ` Rafael 'Dido' Sevilla
2001-11-28 18:00             ` Xavier Leroy
2001-11-30  8:05               ` Sven
2001-11-09 20:54 ` Vitaly Lugovsky
2001-11-09 21:39   ` Patrick M Doane
2001-11-11 12:42     ` Sven
2001-11-11 22:05       ` Tom
2001-11-09 15:55 Dave Berry
2001-11-28 20:29 John Field
2001-11-28 22:08 ` Al Christians
2001-11-29  1:25 ` james woodyatt
2001-11-29  8:47   ` Florian Hars
2001-11-30  7:12     ` james woodyatt
2001-11-29  7:11 Ohad Rodeh
2001-11-29 19:49 David Gurr
2001-11-30  1:18 Don Syme
2001-11-30  1:59 ` Julian Assange
2001-12-01  3:23   ` Richard Stallman
2001-12-04 18:53     ` Sven
2001-12-06  2:46       ` Richard Stallman
2001-11-27 19:10         ` John Field
2001-11-28 18:22           ` Xavier Leroy
2001-11-28 19:14             ` Ronald Kuehn
2001-11-29  0:38             ` Julian Assange
2001-11-29  8:32               ` Xavier Leroy
     [not found]                 ` <20011129105008.DEBFD25A1B@suburbia.net>
2001-11-29 12:50                   ` Xavier Leroy
2001-11-29 13:42                     ` Jérôme Marant
2001-11-29 13:11                 ` Greg Bacon
2001-11-29 23:01                   ` Julian Assange
2001-11-29 23:13                     ` Greg Bacon
2001-11-29  8:31             ` Florian Hars
2001-11-29  8:43               ` Daniel de Rauglaudre
2001-11-29  9:04                 ` Jérôme Marant
2001-11-29  9:15                   ` Xavier Leroy
2001-11-29  9:29                     ` Jérôme Marant
2001-11-29  9:25                   ` Daniel de Rauglaudre
2001-11-29  9:35                     ` Jérôme Marant
2001-11-29  8:53               ` Xavier Leroy
2001-11-30  8:09             ` Sven
2001-12-07  0:09           ` YAMAGATA yoriyuki
2001-12-07  7:11             ` Richard Stallman
2001-12-06 12:26         ` Sven
2001-12-07  3:12           ` Richard Stallman
2001-12-10 15:28             ` Sven
2001-12-10 23:24               ` Jacques Garrigue
2001-12-11  4:22                 ` hooh pxw
2001-12-11 10:19                 ` Sven
2001-12-11  7:15               ` Richard Stallman
2001-11-30  4:25 Gregory Morrisett

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=v1tlmhgpk69.fsf@cs.cmu.edu \
    --to=md5i@cs.cmu.edu \
    --cc=caml-list@inria.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;
as well as URLs for NNTP newsgroup(s).