kdelibs/klauncher license question

[Michael Pyne]

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090218/048dc95b/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090218/048dc95b/attachment.sig>