[Kde-pim] Possible solution.

Ingo Klöcker kloecker at kde.org
Sun Jun 24 20:29:08 BST 2007


On Sunday 24 June 2007 20:55, Tom Albers wrote:
> Op zo 24 jun 2007 20:43 schreef u:
> > The question is now how to deal with libkleo, which is in fact the
> > only library in question after Tills clarifying mail. And that is
> > not being decided by religious wars, only be the simple question if
> > we really need a new module to make it easier for people to
> > recognize the licence nature of the code contained.
>
> how about puting it in a 'gpl' subfolder? It's less ugly as creating
> a kdepimlibs-gpl and a better than dropping the LGPG requirement.

I object. We should have a strict separation between GPL and LGPL code 
in order to avoid
- accidentally using GPL code in LGPL code
- accidentally moving code from the gpl subfolder to another file
- anyone accidentally using GPL code for proprietary software 
development

Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20070624/f044f9e1/attachment.sig>
-------------- next part --------------
_______________________________________________
kde-pim mailing list
kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/


More information about the kde-pim mailing list