A kdepimlibs-gpl module? (Was: KDE/kdepim/libkleo)
Alexander Neundorf
neundorf at kde.org
Tue Jun 26 23:46:09 BST 2007
On Sunday 24 June 2007 19:25, Allen Winter wrote:
> On Saturday 23 June 2007 11:18:57 am Charles Connell wrote:
> > Hey guys,
> >
> > I was going to use Kleo::EncryptionKeyRequester in the Cryptography
> > plugin preferences page to ask for the user's secret key. Right now there
> > is code taken from KGpg, and writing something twice is not good. I
> > figured that for the time being it would be best to make the plugin (not
> > all of kdenetwork) need kdepim. Of course, the best thing in the end
> > would be to move libkleo to kdepimlibs so that it can be properly used
> > like a library.
> >
> > - Charles
> >
> > PS. I can hold onto this until after they branch for KDE 4 releases, to
> > keep things how they are for now. Just tell me what you think.
>
> Status Update:
> The kleo library will not be relicensed to the LGPL.
> So, the kleo library will not be relocated to the kdepimlibs module.
>
> Several options are floating around now:
> 1. create a new kdepimlibs-gpl module for libkleo and a few other
> useful libraries that must remain GPL for various reasons.
So we have a huge kdelibs, a small kdepimlibs and an even smaller kdepimlibs
module and all other modules don't have a libs module at all ?
How about moving kdepimlibs to kdelibs and creating a new kdelibs-gpl ?
kdebase depends on it anyway (ok, you can also run kde apps without
kdebase... )
Alex
More information about the kde-core-devel
mailing list