Re: kdepim/konsolekalendar [POSSIBLY UNSAFE]
Cornelius Schumacher <[email protected]>
| Newsgroups | gmane.comp.kde.licensing |
|---|---|
| Message-ID | <[email protected]> |
On Wednesday 24 March 2004 00:16, Ingo Klöcker wrote: > > Can you prove your claim about the LGPL > (http://www.gnu.org/licenses/lgpl.html)? I found no indication that > it's allowed to link an LGPL-licensed program to a proprietary > library. LGPL is meant to be used for the other direction, i.e. allow > linking proprietary programs to LGPL-licensed libraries. The LGPL > uses a lot the following term "work that uses the Library". OTOH it > doesn't talk about "libraries that the Library uses". Does linking really have a direction? Linking means putting together. konsolekalendar won't work without Qt and the Qt library without konsolekalendar won't do anything useful either. So konsolekalendar using the proprietary version of Qt is a "work that uses the Library", where "Library" means konsolekalendar. I think that's pretty clear. > Please explain why you think that LGPL allows linking to proprietary > libraries. As I mentioned in my other message GNU specifically > recommends to use GPL + exception if one wants to link to a > QPL-licensed library. If LGPL would be an alternative then they would > have mentioned it. Well, the FSF strongly advises against using the LGPL, so they don't mention it at all, if possible. For example there isn't a LGPL FAQ like the GPL FAQ, although there are certainly as many frequently asked questions about the LGPL as the GPL. -- Cornelius Schumacher <[email protected]>