Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: skaller <skaller@users.sourceforge.net>
To: Sven Luther <sven.luther@wanadoo.fr>
Cc: Markus Mottl <markus.mottl@gmail.com>,
	yaron jane <yminsky@janestcapital.com>,
	Florian Hars <florian@hars.de>, ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] ANN: Sexplib - library for S-expression conversions
Date: Wed, 09 Nov 2005 20:25:26 +1100	[thread overview]
Message-ID: <1131528326.13828.93.camel@rosella> (raw)
In-Reply-To: <20051109085716.GA24776@localhost.localdomain>

On Wed, 2005-11-09 at 09:57 +0100, Sven Luther wrote:
> On Wed, Nov 09, 2005 at 07:42:19PM +1100, skaller wrote:
> > On Tue, 2005-11-08 at 13:29 -0500, Markus Mottl wrote:
> > 
> > > Sorry for the confusion, but I should have mentioned in my
> > > announcement that it is available under the LGPL including the special
> > > exception also employed by INRIA to work around the linking
> > > restrictions.  
> > 
> > 
> > I use the acronym
> > 
> > 	LGPLX
> > 
> > for that licence.
> 
> What about LGPL-OCAML ? 

Fine by me, though I note that LGPL with linking exemption
need not be restricted to Ocaml: if others adopted this,
for example for C packages, the OCAML would be a misnomer.
OTOH LGPL-OCAML is more suggestive in the case of Ocaml
codes.

BTW: for Debian GPL and LGPL licences do not have to
be provided in full, since they're installed automatically
in /usr/share somewhere. It would be nice if LGPLX/LGPL-OCAML 
was treated the same way.

Although GODI cannot do it yet, eventually it would be nice
to be able to constrain and/or report licences when building
packages -- which requires a licencing system with centralised
licences with recognized keys and behaviour rules.

Maybe INRIA, Gerd and Sven can get together and agree on
an acronym, and also get the licence certified by OSS?

IMHO this licence is a pretty good compromise: it prevents
'closed source' being distributed fully closed, but it doesn't
prevent closed source being used to generate closed binaries,
nor does it prevent closed source being distributed along
with open source (provided that open source remains open).

AFAICS it only 'infects' sources if one derives from
a combination of the open and closed source, then the
closed sources must be opened.

-- 
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net


  reply	other threads:[~2005-11-09  9:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-07 23:09 Markus Mottl
2005-11-08 15:46 ` [Caml-list] " Florian Hars
2005-11-08 18:29   ` Markus Mottl
2005-11-09  8:42     ` skaller
2005-11-09  8:57       ` Sven Luther
2005-11-09  9:25         ` skaller [this message]
2005-11-08 16:04 ` N. Owen Gunden
2005-11-09  2:09 ` N. Owen Gunden

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=1131528326.13828.93.camel@rosella \
    --to=skaller@users.sourceforge.net \
    --cc=caml-list@inria.fr \
    --cc=florian@hars.de \
    --cc=markus.mottl@gmail.com \
    --cc=sven.luther@wanadoo.fr \
    --cc=yminsky@janestcapital.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