split kdepimlibs

[laurent Montel]

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 ?

> 
> 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