> So if this an intermediary malheur, we should get libcalendaring into > Debian until this is fixed properly upstream. Important to my > supportive disposition on this is, that someone from upstream is > actively working on a server-side usable kdepimlibs. If that is the > case I can reason with other DDs if the issue of code duplication > comes up. For now, I consider libcalendaring as a maintained and > minimalized fork of kdepimlibs that is a requirement for getting the > server-side part of Kolab (and also the webmailers) into Debian. > > My Kolab2 server is getting old, so let's get this thing rocked for > Debian jessie!!!
I mentioned the libcalendaring thing in #debian-qt-kde, Sune Vuorela (svuorela) listed these as his requirements for libcalendaring getting into Debian. 1) libcalendaring-* doesn't have a single symbol in common with kdepimlibs *and* 2) there are two versions of libkolab(-xml) that doesn't conflict and 3) these versions of libkolab(-xml) doesn't share symbols, then I can start withdraw my objections Diane
signature.asc
Description: This is a digitally signed message part.
