From: Brian Rogoff <bpr@best.com>
To: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] CDK license
Date: Wed, 30 May 2001 20:11:56 -0700 (PDT) [thread overview]
Message-ID: <Pine.BSF.4.21.0105301958510.10735-100000@shell5.ba.best.com> (raw)
In-Reply-To: <20010531112732Q.garrigue@kurims.kyoto-u.ac.jp>
On Thu, 31 May 2001, Jacques Garrigue wrote:
> On the same line of thought, the ocaml compiler is released under the
> QPL, which is not compatible with the GPL.
> This means that you cannot build a toplevel including any library
> under the GPL, since it would be in contradiction with either of the
> two licenses.
> At the very least, it seems necessary to add a clause to the GPL,
> saying that linking to QPLed libraries is allowed, just as RMS himself
> suggested for KDE software.
At this point, I'd suggest that we _really_ need to consult a lawyer who
is familiar with intellectual property law and the GPL.
As far as libraries go, I think the LGPL is a fair compromise between the
really dedicated RMS followers (once affectionately referred to as
"license ayatollahs" on this very list :) and those who are willing to
tolerate a variety of kinds of software, including proprietary. I
understand the reasons for going GPL instead of LGPL ("resistance is
futile, prepare to be assimilated, or don't use this code") but if it's
going to be that way then I don't want my Consortium dues to fund work
on the CDK.
> Another remark is that lablgtk-1.2.0 contains a COPYING file, saying
> that the library itself is LGPL, examples are more or less public
> domain, and applications are _not_ open source. Claiming that all this
> is GPL is clearly wrong. This COPYING is not there, and no README file
> either, which is the only documentation for lablgtk :-)
>
> (This is not a rant: I am the one who didn't check)
It's a tricky business, this license stuff, and a lot less fun than coding ;-).
-- Brian
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-05-31 3:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-30 19:06 Brian Rogoff
2001-05-31 1:05 ` rbw3
2001-06-06 7:05 ` Sven LUTHER
2001-06-06 7:42 ` Sven LUTHER
2001-05-31 2:27 ` Jacques Garrigue
2001-05-31 3:11 ` Brian Rogoff [this message]
2001-05-31 7:46 ` Fabrice Le Fessant
2001-06-06 7:40 ` Sven LUTHER
2001-06-06 8:36 ` reig
2001-06-06 8:51 ` Sven LUTHER
2001-06-06 9:01 ` [Caml-list] question about modules Mark Wotton
2001-06-06 10:01 ` Markus Mottl
2001-06-06 13:17 ` Mark Wotton
2001-05-31 22:05 ` [Caml-list] CDK license John Max Skaller
2001-06-06 9:44 Dave Berry
2001-06-06 10:04 ` Sven LUTHER
2001-06-06 15:44 ` Stefan Monnier
2001-06-07 1:25 ` Jacques Garrigue
2001-06-08 12:59 ` Sven LUTHER
2001-06-07 9:03 ` Joerg Czeranski
2001-06-06 10:24 Dave Berry
2001-06-06 16:24 ` Brian Rogoff
2001-06-08 13:27 ` Sven LUTHER
2001-06-08 15:35 ` Brian Rogoff
2001-06-08 13:24 ` 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=Pine.BSF.4.21.0105301958510.10735-100000@shell5.ba.best.com \
--to=bpr@best.com \
--cc=caml-list@inria.fr \
--cc=garrigue@kurims.kyoto-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