[Kde-pim] split kdepimlibs

[Daniel Vratil]

On Tuesday 26 of August 2014 19:02:49 laurent Montel wrote:
> Le mardi 26 août 2014 18:25:01 Daniel Vratil a écrit :
> > On Tuesday 26 of August 2014 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)
> > 
> > Hi,
> > 
> > I definitely want to have the Server and the client libraries in one repo,
> > shipped as a complete solution for PIM storage with the server being just
> > part of the solution, not a standalone one. My original idea was that we
> > would just merge the client libs into the existing akonadi.git repo, but
> > setting up new akonadi-framework.git works just fine with me (and
> > akonadi.git end up like kdelibs.git)
> 
> seems good for me
> 
> And we move serialize plugin from kdepim-runtime to this framework no ?

The plugins usually depend on the type-specific classes, so they would have to 
go to the "Extras" too.

> > About the type-specific (-abc, -calendar, ...) frameworks: maybe there
> > could be something like Akonadi Framework Extras, and Akonadi Framework
> > would really only be the server and the base client libs? What do you
> > think?
> I like it
> 
> > Dan

-- 
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/793f3c2b/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/