caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Sven LUTHER <luther@dpt-info.u-strasbg.fr>
To: Brian Rogoff <bpr@best.com>
Cc: Dave Berry <Dave@kal.com>,
	Sven LUTHER <luther@dpt-info.u-strasbg.fr>,
	reig@dcs.gla.ac.uk, caml-list@inria.fr
Subject: Re: [Caml-list] CDK license
Date: Fri, 8 Jun 2001 15:27:20 +0200	[thread overview]
Message-ID: <20010608152720.D12090@lambda.u-strasbg.fr> (raw)
In-Reply-To: <Pine.BSF.4.21.0106060909490.6656-100000@shell5.ba.best.com>

On Wed, Jun 06, 2001 at 09:24:12AM -0700, Brian Rogoff wrote:
> > If your main aim is to protect your code from unwanted use, then go
> > ahead and use the GPL or LGPL.  If your main aim is to get your code
> > used as widely as possible, use a less restrictive license.  Surely the
> > aim of the CDK is to promote wide use, rather than to restrict it?
> 
> That's my take on it. Besides, if I use someone else's library in a
> commercial product, it seems that it would be in my best interests to
> contribute fixes and enhancements. That's why I don't mind an LGPL like 

Yes, that's the main point here. It would be in your best interrest and that
of the ocaml community as well.

> approach which forces me to do so. What I don't want to do is to use
> someone's library for some data structure and then have *all* of my code 
> forced to accept that license.

The LGPL don't force you to do that, but i think many people think such, is it
not ? That's the main reason why it was created instead of just using the GPL
for libraries.

Friendly,

Sven Luther
-------------------
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


  reply	other threads:[~2001-06-08 13:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-06 10:24 Dave Berry
2001-06-06 16:24 ` Brian Rogoff
2001-06-08 13:27   ` Sven LUTHER [this message]
2001-06-08 15:35     ` Brian Rogoff
2001-06-08 13:24 ` Sven LUTHER
  -- strict thread matches above, loose matches on Subject: below --
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-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
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-05-31 22:05 ` John Max Skaller

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=20010608152720.D12090@lambda.u-strasbg.fr \
    --to=luther@dpt-info.u-strasbg.fr \
    --cc=Dave@kal.com \
    --cc=bpr@best.com \
    --cc=caml-list@inria.fr \
    --cc=reig@dcs.gla.ac.uk \
    /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).