A kdepimlibs-gpl module? (Was: KDE/kdepim/libkleo)
Justin Karneges
justin at affinix.com
Mon Jun 25 02:08:05 BST 2007
On Sunday 24 June 2007 4:25 pm, 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.
> 2. keep libkleo and its dependencies in kdepim and have
> kopete (i.e. kdenetwork) depend on kdepim
> 3. move kopete into kdepim
> 4. ??
FWIW, QCA supports PGP and is LGPL. I'm not sure how it would fit into the
kleo scheme, but I just thought I'd mention it.
-Justin
More information about the kde-core-devel
mailing list