Re: GPL/LGPL confusion
On Sun, 1 Jul 2001, Ben Burton wrote: 1. Can I package an LGPL library foo that links with a GPL library bar? Only if the GPL library is not required for basic operation of the LGPL library. This might be because there are non-GPL versions of the GPL library with looser licenses, or because the GPL library only provides optional features. Otherwise the LGPL library needs to be under the regular GPL. Just because something is a library, doesn't mean you can put it under the LGPL when it would otherwise have to be full GPL. If the two libraries just happen to be together, and the LGPL library will use the GPL library only if it is available, then programs that use only the LGPL library are not affected. 2. If so, is it appropriate to put a notice in the copyright file for foo that this library links with a GPL library and thus any software that links with foo must be GPL-compatible? In general you should not need to do this. Either the library depends on the GPL library (in which case it has to be full GPL) or it does not (in which case it does not matter). I suppose if you had an application program that required the optional GPL-only features from the GPL library, but accessed them through the otherwise LGPL library, that would probably require it to be GPL also.
Re: GPL/LGPL confusion
I am not a lawyer, so please do not rely on this as legal advice. I am also not a Debianite, but I will cc this message to debian-legal so they can avoid duplication of effort. Okay, I've gone through debian-legal archives, I've looked on the FSF site and the summary is that I'm rather confused. 1. Can I package an LGPL library foo that links with a GPL library bar? Yes. The restrictions of the LGPL are a subset of the restrictions of the GPL, even when it comes to the right to add remaining restrictions of the GPL (due to section 3 of the LGPL), so it does not violate section 6 of the GPL. However, as your allude to in your second question, if your library requires the GPL'ed library, the net effect will be almost the same as if your library were GPL'ed. It will only be legal to link GPL-compatible programs with your library (this includes more than just GPL'ed programs, 2. If so, is it appropriate to put a notice in the copyright file for foo that this library links with a GPL library and thus any software that links with foo must be GPL-compatible? As a matter of politeness and good documentation, yes. Adam J. Richter __ __ 4880 Stevens Creek Blvd, Suite 104 [EMAIL PROTECTED] \ / San Jose, California 95129-1034 +1 408 261-6630 | g g d r a s i l United States of America fax +1 408 261-6631 Free Software For The Rest Of Us.
GPL/LGPL confusion
Okay, I've gone through debian-legal archives, I've looked on the FSF site and the summary is that I'm rather confused. 1. Can I package an LGPL library foo that links with a GPL library bar? 2. If so, is it appropriate to put a notice in the copyright file for foo that this library links with a GPL library and thus any software that links with foo must be GPL-compatible? Please CC me on replies; I'm not subscribed. Thanks - Ben. -- Ben Burton [EMAIL PROTECTED] | [EMAIL PROTECTED] http://baasil.humbug.org.au/bab/ Public Key: finger [EMAIL PROTECTED] Most people are other people. Their thoughts are someone else's opinions, their lives a mimicry, their passions a quotation. - Oscar Wilde
