Re: kdepim/konsolekalendar [POSSIBLY UNSAFE]
Ingo Klöcker <[email protected]>
| Newsgroups | gmane.comp.kde.licensing |
|---|---|
| Message-ID | <[email protected]> |
On Tuesday 23 March 2004 08:15, Bo Thorsen wrote: > Sorry for jeopardy-quoting here, but the thread is quite long and my > comment is fairly generic. > > When licensing an application with Qt, there are two choices you can > take: This should read: "When licensing an application for use with the non-GPL Windows version of Qt..." > - LGPL > - GPL + Qt exception 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". 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. Regards, Ingo _______________________________________________ Kde-licensing mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-licensing
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAYMVpGnR+RTDgudgRAodtAJwJ++N5B2WC62QAv5v1GxfJf5aNSQCgqUSc brrSGu13JBcZFNJRbMnPQBs= =2Hsd -----END PGP SIGNATURE-----