kdelibs/klauncher license question

View: New views
2 Messages — Rating Filter:   Alert me  

kdelibs/klauncher license question

by Michael Pyne :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.
Hi all,


While looking into altering the behavior of executing .desktop files in response to the thread on it (and the LWN and slashdot stories) I came across what I believe is a mistake in licensing:


The kdelibs/kinit/proctitle.{h,cpp} files are both licenses GPLv2+ instead of LGPL like the rest of kdelibs.


In this case it is compiled into the executable kdeinit4 (not a library however). So that's kind of a mitigating factor, but is this desired? I guess really the question is does this fall into a "Source file that is part of a library with a public API which is part of KDE Platform" [1]?


klauncher itself is accessed over D-Bus and not linked to directly but it does provide library-like services to KDE applications (and is used as such by various code in kdelibs which *does* get linked in). So is this something that is wrong, technically correct but undesired, or desired licensing? (The other files in klauncher are licensed LGPL...)?


Regards,
- Michael Pyne


[1] http://techbase.kde.org/Policies/Licensing_Policy para. 3



_______________________________________________
Kde-licensing mailing list
Kde-licensing@...
https://mail.kde.org/mailman/listinfo/kde-licensing

signature.asc (204 bytes) Download Attachment

Re: kdelibs/klauncher license question

by Bugzilla from kde@randomguy3.me.uk :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Thursday 19 February 2009 01:44:08 Michael Pyne wrote:

> The kdelibs/kinit/proctitle.{h,cpp} files are both licenses GPLv2+ instead
> of LGPL like the rest of kdelibs.
>
> In this case it is compiled into the executable kdeinit4 (not a library
> however).  So that's kind of a mitigating factor, but is this desired?  I
> guess really the question is does this fall into a "Source file that is
> part of a library with a public API which is part of KDE Platform" [1]?

It doesn't matter, because proctitle.{h,cpp} are only in an application, not a
library.  Note that the D-Bus interface does not propagate the GPL, only
proper linking (in the compiler sense) does.

The reason it is under the GPL is that they come from another project (an FTP
daemon, if memory serves me correctly, though I'm not sure which one) that is
licensed under the GPL.

Alex



--
Why have I got six monitors?  Because I haven't got room for eight.
  -- Terry Pratchett



_______________________________________________
Kde-licensing mailing list
Kde-licensing@...
https://mail.kde.org/mailman/listinfo/kde-licensing

signature.asc (204 bytes) Download Attachment