Re: libkolab
"Jeroen van Meeuwen (Kolab Systems)" <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kolab |
|---|---|
| Message-ID | <61ea61f17d7d1e20f93360488423382d__29742.6610523418$1366790240$gmane$org@kolabsys.com> |
On 2013-04-23 14:30, Paul Klos wrote: > To summarize, even if we can separate between a Debian libkolab and > Kolab-provided libkolab, there is no guarantee that that will never > cause conflicts. Whereas if the Debian libkolab and Kolab-provided > libkolab are one and the same, you can be sure there will be no > conflicts. > > And the reality is, that there will be no Debian libkolab, as long as > libcalendaring is somehow involved. > libkolab is only supposed to be built using libcalendaring for as long as a distribution release (such as Enterprise Linux 6, Fedora <= 16, Debian Squeeze and Wheezy, and others) does not provide sufficiently up to date KDE PIM libraries. As soon as the distribution releases do, the problem of pulling in a KDE stack on the server is to be resolved by KDE Frameworks, but not by libcalendaring. Kind regards, Jeroen van Meeuwen -- Systems Architect, Kolab Systems AG e: vanmeeuwen at kolabsys.com m: +44 74 2516 3817 w: http://www.kolabsys.com pgp: 9342 BF08