public inbox for
 help / color / mirror / Atom feed
From: Ross Johnson <>
Subject: Re: changing pthreads-win32 license
Date: Fri, 31 Oct 2003 07:00:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Alexander Terekhov wrote:

>>It specifically exempts macro definitions and the like.  Read it.
>You mean "ten lines or less in length"? Yeah, given that the 
>length of lines seem to be unrestricted. [L]GPL is totally 
>brian-damaged technically and legally. Really.
Personally, I'd be inclined to regard any work that included only
the unmodified LGPL'ed header files, specifically supplied for that
purpose, and dynamically linked to the unmodified main body of the
library, to be an independent and separate work as far as the LGPL
goes - static linking and assorted tricks aside for the moment.

If the LGPL really doesn't permit that, then I'd be in favour of
changing to an appropriate alternative license. But for the moment
I'm trying to convince myself that the CPL (Alexander's preferred
license) would serve the purpose any better if it was adopted.

I still don't see how the CPL differs fundumentally from the LGPL with
it's so-called 'virus' effect.

Here's the URL for the CPL again:

- OK, it relies on some common definition of 'derivative work'.
- section 1/b/ii appears to regard any distributed derivative
work as a 'Contribution' to the 'Program' I.e. is covered by
the CPL. I note that this does not confine the term only to code
contributed to the primary project maintainer/s for includion.
- NOW, section 3/b/iv then effectively says that re-distribution
of the CPL'ed 'Program' (which is now the combined derivative work)
is only allowed if, amongst other things, the source code for the
[combined] work is made accessible.

Using the aformentioned (in a previous message) libstdc++ library as
the example,

if the library was CPL'ed, how would the CPL free the author of a
program that uses this library from having to disclose the full program
source code?


  parent reply	other threads:[~2003-10-31  7:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2003-10-20 10:06 ` Alexander Terekhov
2003-10-30  7:03   ` Ross Johnson
2003-10-30  9:51     ` Alexander Terekhov
2003-10-30 10:49       ` Will Bryant
2003-10-30 11:17         ` changing pthreads-win32 license - Practical Comment James Ewing
2003-10-30 11:46         ` changing pthreads-win32 license Alexander Terekhov
2003-10-30 13:14           ` UNSUBCRIBE Geoffrey Atkinson
2003-10-31  7:00           ` Ross Johnson [this message]
2003-10-31 10:56             ` changing pthreads-win32 license Alexander Terekhov
2003-10-31 16:27             ` Phil Frisbie, Jr.

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).