From: Brian Rogoff <bpr@bpr.best.vwh.net>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: "Rafael 'Dido' Sevilla" <sevillar@team.ph.inter.net>,
Patrick M Doane <patrick@watson.org>,
Caml List <caml-list@pauillac.inria.fr>
Subject: Re: [Caml-list] License Conditions for OCaml
Date: Fri, 9 Nov 2001 16:40:30 +0000 (GMT) [thread overview]
Message-ID: <Pine.BSF.4.10.10111091629320.38871-100000@bpr.best.vwh.net> (raw)
In-Reply-To: <20011109094545.A4395@pauillac.inria.fr>
On Fri, 9 Nov 2001, Xavier Leroy wrote:
> > Yeah, this is a slightly misleading statement, unless the OCaml
> > development team has made a modification to the LGPL similar to what was
> > done for the Guile license, which is LGPL with one additional clause:
> > blanket linking is allowed for Guile. (OCaml dev team, is this also the
> > license under which the runtime exists?)
>
> We haven't yet modified the LGPL to remove these silly restrictions on
> linking with LGPL code, but plan to do so in the near future.
>
> We'd be interested in examples of other software projects that did this.
> You mention Guile, however it seems to be under the (standard) GPL
> (not even LGPL).
GNAT, www.gnat.com, also uses a modified standard GPL. They've been doing
it for a while, and they even have commercial customers. Here's the whole
damned thing
--
-- This is free software; you can redistribute it and/or modify it under
-- terms of the GNU General Public License as published by the Free Software
-- Foundation; either version 2, or (at your option) any later version.
-- This software is distributed in the hope that it will be useful, but WITH
-- OUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
-- or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
-- for more details. Free Software Foundation, 59 Temple Place - Suite
-- 330, Boston, MA 02111-1307, USA.
--
-- As a special exception, if other files instantiate generics from this
-- unit, or you link this unit with other files to produce an executable,
-- this unit does not by itself cause the resulting executable to be
-- covered by the GNU General Public License. This exception does not
-- however invalidate any other reasons why the executable file might be
-- covered by the GNU Public License.
Why not just translate Ada jargon to OCaml and swipe this?
-- Brian
-------------------
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
next prev parent reply other threads:[~2001-11-11 10:37 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 [this message]
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 ` [Caml-list] " Michael Welsh Duggan
2001-11-09 8:59 ` 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=Pine.BSF.4.10.10111091629320.38871-100000@bpr.best.vwh.net \
--to=bpr@bpr.best.vwh.net \
--cc=caml-list@pauillac.inria.fr \
--cc=patrick@watson.org \
--cc=sevillar@team.ph.inter.net \
--cc=xavier.leroy@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