public inbox for
 help / color / mirror / Atom feed
From: Alexander Terekhov <>
To: "Gili" <>
Cc: "Phil Frisbie, Jr." <>,
Subject: Re: Static linking under win32
Date: Mon, 06 Dec 2004 18:53:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> I think the point of conflict is more about what people
> *percieve* LGPL to be about.

BTW, here's rather interesting review of the [L]GPL by OSI's

"These sections of the LGPL are an impenetrable maze of
 technological babble. They should not be in a general-purpose
 software license. The LGPL even concedes that “the threshold
 for this to be true is not precisely defined by law.” (LGPL
 section 5.) A licensee under these provisions won’t have a
 clue how extensive his or her good faith efforts must be when
 creating a derivative work in accordance with sections 2(d)
 and 5 of the LGPL.
 The LGPL, therefore, is an anomaly -- a hybrid license intended
 to address a complex issue about program linking and derivative
 works. It doesn’t solve that problem but merely directs us back
 to the main event, the GPL license itself."

Well, I guess the idea is to simply convert LGPL'ed works to the
"plain" GPL (the LGPL allows this) and stick to the OSI's much
more reasonable (first sale aside for a moment) interprepretation
completely ignoring FSF's politically motivated licensing
smokescreens (I mean their FAQ/quiz/essays/manifestos/etc.)

Now enjoy reading that sample chapter (and consider buying that
book as a whole ;-) ).


       reply	other threads:[~2004-12-06 18:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2004-12-06 18:53 ` Alexander Terekhov [this message]
     [not found] <>
2004-12-06  7:52 ` Ross Johnson
2004-12-06  9:57   ` Alexander Terekhov
2004-12-06 10:46   ` Keresztfalvi Laszlo
2004-12-06 17:35     ` Phil Frisbie, Jr.
2004-12-06 17:47       ` Gili
2004-12-06 18:07       ` Alexander Terekhov
     [not found]       ` <>
2004-12-06 20:08         ` Keresztfalvi Laszlo
     [not found] <>
2004-12-06  6:22 ` Ross Johnson
2004-12-06  6:35   ` Gili
2004-12-06  3:37 Gili

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).