[pkg-kolab] kdepim and kolab

[Diane Trout]

> What is the correct Debian way of creating it? I could add touch to the
> rules file somewhere, but I am assuming that some debhelper magic 
should
> have set the package up instead. Also, pykolab isn't python-kolab, but it
> is in the pykolab.xml package that I see this kolab importing going on.
> 
> Maybe I'll review what the Ubuntu people did, if anything, and I'll also
> check to make sure that python-kolab is a known dependency of 
pykolab.
> 

In my opinion the correct way of creating it would be to create a patch file 
that fixes the kolab build system to create it. (And then submit that 
upstream).

Because if someone wanted to build outside of the packaging they'd 
probably like the kolab package to be importable.

Also for libkolab / libkolabxml to actually be released in debian they 
probably will need symbols files.

I made some progress on a symbols file for libkolabxml.

https://github.com/detrout/debian-libkolabxml/commit/45642c393c818dce408b51de59a871d18985995a

Diane
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-kolab-devel/attachments/20140624/5eb1f57e/attachment.html>