Re: changing pthreads-win32 license

[Ross Johnson <rpj at callisto dot canberra dot edu dot au>]

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:

http://www.opensource.org/licenses/cpl.php

- 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,

http://gcc.gnu.org/onlinedocs/libstdc++/17_intro/license.html

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?

Ross