[pkg-kolab] Kolab debian packages - current state
kolab at klos2day.nl
Thu Nov 28 21:15:25 UTC 2013
Just a recap of my understanding so far and some questions as well.
So, I created an account on alioth and requested access to the collab-maint project on alioth.
4 kolab-related projects have already been created:
- roundcube-plugins-kolab - is this the old package by this name, or roundcubemail-plugins-kolab renamed?
These are not all, but should give us a good starting point.
We also have one bug (#724845, spelling error in control file) against the current libkolab_0.4.2-7 in debian, and also a packaging request (#730600).
I've synced libkolab with what was in the kolab packaging repos, so libkolab on alioth is now at 0.4.2-7 as well.
I've imported upstream version 1.0.1 of libkolabxml, but I haven't been able to build it yet.
Since libkolab depends on libkolabxml, I reckon we need to get libkolabxml upgraded first, then work on libkolab, of which there is also a newer upstream version.
Current roundcube version in sid/jessie is 0.9.5, whereas kolab has a 1.0 development version. I'm not sure what's the minimum required version for kolab 3.1, but maybe we'll need to get that upgraded for roundcubemail-plugins-kolab.
When these packages were hosted on the kolab repository, I used the debian/patches dir. I read about using patch branches, but haven't in fact used them. Is there a debian best practice?
I think we should have a close look at the various kolab meta-packages and fix the dependencies, because this has been a weakness in the debian packages so far. Providing the providing the possibility to install kolab across multiple servers (for example separate ldap, web and mail servers) would be a major improvement.
Finally, is there an IRC channel where people hang out? Sometimes that's easier than email
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: This is a digitally signed message part.
More information about the pkg-kolab-devel