libkolab

All,

Libkolab version 0.4.2. has now been packaged for Debian. However, as long as it depends on libcalendaring, there is no chance it will find its way into Debian.

The only way this is going to happen is if libkolab only depends on kdepimlibs, which will mean pulling in the kde stuff on the server as well.

We thought about creating 2 versions of libkolab, but that's not going to work either. For example, someone using KDE would not be able to test-install a kolab server on his workstation, because he'd end up with 2 conflicting versions of libkolab. Also, 'the possibility of loading two symbols of the same name into the same process is a no-go' - one of the milder quotes from my IRC talk :-).

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?

Paul

_______________________________________________
Kolab-devel mailing list
[email protected]
https://www.intevation.de/mailman/listinfo/kolab-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iQIcBAABCAAGBQJRdZsuAAoJEHtCjbaP5uC9HYEP/3RhGVivnSSRzPA+5I0v1vpq
qtFdbc95OvXlh+edswiHgQ5jGzXJ8M8ptOeMUdjBF7T6nfSK2AEF3nrqhBfEPhL6
hdU82XrFXlIyCcD49ELINfl2FY97a/3feukHIyHr2hecMdvd5UnG1v4w+F84PXE9
Pqcejko7EMFOHjqwOiDe95qYhjOM42+5eJkM6SA+YWPRguEscDx+421imbAh+BIT
8ROkQseuWyW37+apOwHVzPGiLDT7OLcgmUoixYDH70uIg9F2DuCbgci0oeJPGgUd
nObd10KeoezNKz3Pwa+Ex4AVlnxjEfW1+liJXqt24Ls4BdaKoPkbcKDP1WQyWNMz
OWhuZlgj1+gKabvQVc31M2gl7VmJr3QrosAOr5XYkS+TAeQmcLKJ3k7DMTuKU75u
iKFnv6TcR7WSnnr7sWv703AluXpYoJ5+EA6OB06Zw43o00xMXw1ti8pQ9E/YDgeK
43hf1zoLLKfO2Ll/2cUGWI0S+n7Y4braCgpAXt69fneyG5JeXdmXpnraGhYvT0Ed
V9SDttTTdDN+XDzacj4A4LdSbHPbz0ZviY7pWjUnM0hEB7YQNMrh/Ehsq2HRZD8Z
Nw61W6UXL2qkmcQQV+D7G9iwyXDvzriBQg8FmQIMpMV/aSQZ8wbVxlRrYOZKNgUr
0KOL34JwpH5mKQN9yU5d
=zjxL
-----END PGP SIGNATURE-----