caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
To: "caml" <caml-list@inria.fr>
Subject: RE: [Caml-list] MLGame library
Date: Wed, 9 Jun 2004 18:10:46 -0700	[thread overview]
Message-ID: <OOEALCJCKEBJBIJHCNJDCEHOHDAB.vanevery@indiegamedesign.com> (raw)
In-Reply-To: <40C7AABB.4030808@1969.ws>

Karl Zilles wrote:
>
> Well, they changed the LGPL a while back to make it a little more
> complicated.  Not only do you have to distribute the source of the
> library you changed, but you also have to distribute *your
> object code*
> in a way that someone can then modify the LGPL library and relink it
> with the code you have written, creating a new executable.  I'm
> paraphrasing, but I think that's what it boils down to roughly.
>
> It's not the worst thing imaginable, but it dulls any interest many
> commercial developers might have in using an LGPL'd library.  The
> 'exception' that he's talking about removes this additional
> requirement, making it as you originally describe.

I was unaware of this.  I'll have to study up on that.

> Xavier will undoubtable be pleased to see another licensing
> discussion
> on the list.  The way these things usually work out, someone
> will soon
> suggest that a 'BSD' license is really the way to go, then we'll see
> about 30 rabid posts arguing the situation from both sides, repeating
> the same arguments that they did 3 months ago when it last broke out.

Looking back, I see I was a part of those threads.  Frankly, I could
care less how people want to license their own software.  I'm only
interested in whether the MLGame people have considered the LGPL, a
license that's potentially useful to me.  I find that a lot of people
who release their first cut of something as GPL, simply haven't thought
through the commercial implications.  They can often be persuaded to
change to LGPL on the grounds of greater utility to a larger audience.
But if they have thought it through and aren't interested, so be it.  No
big deal.  Not everybody's interested in commercial stuff.

What gets me riled up is the zealousy of a lot of people in the GPL
camp.  Charges of MIT / BSD "evil profiteers," "you're just here to rip
us off," "all software should be free," "the contractual service model
is the only valid business model," etc.  I don't respect that kind of
thinking, any more than I respect people who think property rights
shouldn't exist.  Far too many MIT / BSD style projects have proven that
open source under that model works just fine, is enlightened, provides
people with real benefit, is not inequitable, etc.  It all depends on
whether you're into idealistic theory, or what works out in pratice.  My
own idealism is tempered by pragmatism.  I don't like extreme idealists
who are not so tempered.


Cheers,                         www.indiegamedesign.com
Brandon Van Every               Seattle, WA

20% of the world is real.
80% is gobbledygook we make up inside our own heads.

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.693 / Virus Database: 454 - Release Date: 5/31/2004

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2004-06-10  1:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 11:06 Lukasz Lew
2004-06-09 20:16 ` Brandon J. Van Every
2004-06-09 22:36   ` Sylvain LE GALL
2004-06-09 23:59     ` Brandon J. Van Every
2004-06-10  0:26       ` Karl Zilles
2004-06-10  1:10         ` Brandon J. Van Every [this message]
2004-06-10  5:46           ` [Caml-list] [OT] Yet Another Licence War Alan Schmitt
2004-06-18 15:58 ` [Caml-list] MLGame library Blue Prawn

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=OOEALCJCKEBJBIJHCNJDCEHOHDAB.vanevery@indiegamedesign.com \
    --to=vanevery@indiegamedesign.com \
    --cc=caml-list@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).