Re: Something about Less General Public License

[Claude Yih]

Thanks for your kindness~~~

> > Of course, we know that we should distribute our library under
> > LGPL too.
>
> Not necessarily. It all depends on the interaction between the> original LGPL 
> code and your new code.
>

As a matter of fact, We got a new library by modifying the LGPL code
and adding some our own code.

> > However, in our library, it is
> >dynamically linked with a shared library not covered by LGPL (this
> >part is not the one belongts to the library covered by LGPL).
>
> So you have three sets of code linked together:
>
> 1) An LGPL library
> 2) A non LGPL dynamic library.
> 3) Your code.
>
> Right? Or is it:
>
> 1) A non LGPL dynamic library.
> 2) Your code which incorporates some LGPL code

It is as follows:
1) A non LGPL dynamic library
2) Our code which is based on the LGPL code

> It's not yours to distibute under the LGPL. But it doesn't matter.
> There's no requirement that code linked to LGPL code be licensed under
> the LGPL. That's in fact the LGPL's entire purpose.
>
> The only question that remains is how to license your code. And that
> depends on how it interacts with the LGPL code.
>
> > Our question is that if we distributed our library
> >(binary and source code)   under the terms of  Less General Public
> >License without providing the shared library together, would our
> >activity be a violation of Less General Public License?
>
> No matter one way or the other. If you license your code under the
> LGPL, then without a doubt the LGPL license issues from the original
> LGPL code has been addressed. The LGPL has three primary tenets:
>
> 1) LGPL code should remain free.
> 2) Other code linked to LGPL code doesn't have to be licensed under the
> LGPL.
> 3) binary only packages can be released.

1) Well, our source of the new will be free.
2) You mean the shared library linked with our library should be
distributed as well
, but has not to be licensed under the LGPL?

Another question is that if a third party used our library, I mean
statically or dynamically link, to create its own application or
library, would its work has to be licensed under the LGPL?