[Kolab-devel] libkolab

[Torsten Grote]

On Monday 22 April 2013 22:18:48 Paul Klos wrote:
> Is there any objection to letting go of the whole libcalendaring idea, and
> just bite the bullet and pull in kdepimlibs and the rest on a Kolab server
> install?

If I remember correctly, the (temporary) creation of libcalendering was 
intentional and the pros and cons were deliberated upon. As far as I know 
libcalendering was supposed to die as soon as KDE Frameworks is ready (and 
shipped on all of Kolab's platforms) which I think it isn't.

Do you happen to know how other distributions that ship libkolab handle this 
problem?

Maybe it can be a solution to keep libcalendering in the up2date Kolab repo 
and depend on kdepimlibs in the official Debian repo for now. It probably will 
take a while before the entire Kolab server enters Debian upstream and until 
that happens libkolab will be only used to provide Kolab client support for 
Kontact which requires kdepimlibs anyway.

Regards,
Torsten

-- 
Torsten Grote, Kolab Evangelist

Kolab Systems AG, Zürich, Switzerland

e: grote at kolabsys.com
t: +41 43 501 66 91
w: http://kolabsys.com

pgp: 274D 4F97 Torsten Grote
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 316 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20130423/bf6e392c/attachment.sig>