split kdepimlibs

[Kevin Ottens]

Hello,

On Tuesday 26 August 2014 18:25:01 Daniel Vratil wrote:
> 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.

Excellent. Definitely what I'd like to see happen.

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

If we could keep the akonadi repository that would be nice. I'm not too fond 
of the "-framework" suffix in the repository name.

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

Makes sense. An akonadi-extras is a possibility.
 
Regards.
-- 
Kévin Ottens, http://ervin.ipsquad.net

KDAB - proud supporter of KDE, http://www.kdab.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20140826/57b1d84a/attachment.sig>