[Kde-pim] split kdepimlibs

[Daniel Vratil]

On Tuesday 26 of August 2014 17:29:46 Kevin Krammer wrote:
> On Tuesday, 2014-08-26, 12:32:48, laurent Montel wrote:
> > Le mardi 26 août 2014 11:50:50 Kevin Ottens a écrit :
> > > On Tuesday 26 August 2014 11:20:25 laurent Montel wrote:
> > > > Hi,
> > > > I will split kdepimlibs as it
> > > > 
> > > > akonadi (need to find another name because it's still used)
> > > > akonadi-abc
> > > > akonadi-calendar
> > > > akonadi-contact
> > > > akonadi-mime
> > > > akonadi-notes
> > > > akonadi-socialutils
> > > 
> > > To me it sounds like some of those things could be regrouped now. What
> > > about also bringing the akonadi server on board? Having a bigger akonadi
> > > framework containing server (right now in kdesupport), some access libs
> > > and a few default plugins would make sense (it looks like a KIO like
> > > framework).
> > 
> > Regroup as a framework as :
> > akonadi-framework (better name)
> > 
> >  -> src
> >  
> >      -> akonadi-abc
> >      -> akonadi-calendar
> >      -> akonadi-contact
> >      -> akonadi-mime
> >      -> akonadi-notes
> >      -> akonadi-socialutils
> >      -> server (Dan must speak about it if he wants to move here)
> >      -> plugins serializer (moved from kdepim-runtime)
> 
> We have to assume that frameworks will end up in single package
> dependencies, so it would be nice to have Akonadi server separate so it
> remains installable on its own.

Ee, the server goes in :-) It will still be installable standalone of course, 
the only difference is that what is now libakonadiprotocolinternals.so would 
be libKF5AkonadiPrivate.so.

> 
> One thing that should probably be considered is that the current libs mix
> non- UI and UI stuff, so some separation in between these lines might still
> be something to strive for.

The Akonadi framework itself is already split into multiple libraries:

libKF5AkonadiCore - non-gui stuff
libKF5AkonadiAgentBase - agents/resources-related stuff (non-gui)
libKF5AkonadiWidgets - gui
(and some more, not important)

I think all the type-specific libraries (-abc, -calendar, ...) would all 
depend on the Widgets library anyway and the amount of non-gui stuff is rather 
limited *


* I haven't actually checked, sorry ;)

> 
> > > > gpgme++
> > > > kabc
> > > > kalarmcal
> > > > kblog
> > > > kcalcore
> > > > kcalutils
> > > 
> > > This one looks like a dumping ground of random things. Maybe some of it
> > > should move in other frameworks?
> > 
> > Sergio can speak about it
> > 
> > > > kholidays
> > > > kimap
> > > > kioslave
> > > 
> > > Definitely not a framework. Are all the ioslaves in there still used? I
> > > think at least some of them can be let go. The others could go in
> > > kio-extras I guess.
> > 
> > kioslave indeed not a framework. I think that just pop3 is used by kdepim
> > 
> > yes others can move to kio-extra
> 
> Is the Akonadi IO slave in there as well?
> 
> Cheers,
> Kevin

-- 
Daniel Vrátil | dvratil at redhat.com | dvratil on #kde-devel, #kontact, #akonadi
KDE Desktop Team
Associate Software Engineer, Red Hat

GPG Key: 0xC59D614F6F4AE348
Fingerprint: 4EC1 86E3 C54E 0B39 5FDD B5FB C59D 614F 6F4A E348
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20140826/6d1c8f77/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/