From: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
To: aaron_ogden_2000@yahoo.com
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] LGPL Exception Question
Date: Fri, 04 Apr 2008 08:53:27 +0900 (JST) [thread overview]
Message-ID: <20080404.085327.233450447.garrigue@math.nagoya-u.ac.jp> (raw)
In-Reply-To: <200863.53048.qm@web52304.mail.re2.yahoo.com>
From: Aaron Ogden <aaron_ogden_2000@yahoo.com>
> Part of the LGPL that INRIA(and many others) use
> states:
> "Everyone is permitted to copy and distribute
> verbatim copies
> of this license document, but changing it is not
> allowed."
>
> If INRIA nor anyone else is not allowed to change the
> LGPL, how is it that the special linking exception is legal?
You are not allowed to change the document, but you are perfectly
allowed to define your own license by adding extra clauses or
exceptions to it. This is what ocaml does: the license text is copied
verbatim, but an exception is indicated prior to it, and in each
covered file.
This is a bit like the QPL: the original must me distributed
unmodified, but patches are OK.
GCC itself does it, by introducing an exception to the GPL for libgcc.
Jacques Garrigue
prev parent reply other threads:[~2008-04-03 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 23:03 Aaron Ogden
2008-04-03 23:53 ` Jacques Garrigue [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=20080404.085327.233450447.garrigue@math.nagoya-u.ac.jp \
--to=garrigue@math.nagoya-u.ac.jp \
--cc=aaron_ogden_2000@yahoo.com \
--cc=caml-list@yquem.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).