Re: libkolab
Torsten Grote <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kolab,gmane.comp.kde.kolab.devel |
|---|---|
| Organization | Kolab Systems AG |
| Message-ID | <2305702.j57OUvoU92@t7laptop1> |
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: [email protected] t: +41 43 501 66 91 w: http://kolabsys.com pgp: 274D 4F97 Torsten Grote _______________________________________________ Kolab-devel mailing list [email protected] https://www.intevation.de/mailman/listinfo/kolab-devel
signature.asc
(application/pgp-signature, 316 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iJwEAAECAAYFAlF2Q7cACgkQwMSfEyyeKRRUBAQAhsfveZxMibD06r/muD73NJQ0 DJb6MlU9QKXIO4FbeDv9XWycxeWNROT5OVIRuBRqBo0UYstvQoqJhc+xudgfBYZA AdCG3BWJpoX5u6E0AHODLqaPL30EgZqW9UQ7GdnS0UIS09Xm+fgz7DLixFVnYvdz hAC997GxShJ2ACfERiI= =UOEZ -----END PGP SIGNATURE-----