[Kde-pim] RFC: Creating kdepimlibs-experimental

[Christophe Giboudeaux]

On Saturday 22 August 2009 16:40:41 Dr. Robert Marmorstein wrote:
> > - Create kdepimlibs-experimental and release them in a separate tarball
> > (that's what is done for kdelibs currently)
> 
> What would go in this tarball?  Would kpilot move here?  Or would only
> akonadi_next (and contacts/) move here?

Only some libraries will go there, akonadi_next, contact and maybe libkrss if 
akregator from the porting branch is moved in kdepim.

> 
> Would this mean adding some CMake magic to enable kpilot only if
>  kdepimlibs- experimental is installed?

that means the weekly snapshots (made by Dirk) would have two tarballs for 
kdepimlibs, one being kdepimlibs-experimental. 

kdepim will then require both kdepimlibs and kdepimlibs-experimental (and 
KPilot/Kaddressbook will be packaged again).

Christophe.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20090822/16a0df6e/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/