Re: [Kolab-devel] Solution for libkolab and kdepimlibs

Hey,

after some discussion we came up with a solution for the problem with 
libkolab, kdepimlibs and kolab server/client. The basic problem is, that on 
the one side we do not want a whole kde installed at the server on the other 
side kolab client needs a libkolab built with kdepimlibs.

The solution we came up with is quite easy: 
* Keep the libkolab the same than before and built it against libcalendaring.
* Make sure that the version of libkolab built with kdepimlibs is everytime 
higher than the coresponding version built against libcalendaring. When I say 
higher version I'm mean something like libkolab0.6.0-1 (in the kolab repo) 
getting libkolab0.6.0-1+pimlibs1 for kolab-client repo.

Regads,

sandro
--
Am Mittwoch, 18. Februar 2015, 10:48:01 schrieb Sandro Knauß:
> Hey,
> 
> > This is about libkolab needing recent kdepimlibs though, not the
> > kolab-desktop-client repositories.
> 
> And I'm talking about that  kolab-desktop-client needs libkolab build with
> kdepimlibs and not with libcalendaring. If we ship the same libkolab build
> once with libcalendaring and once with kdepimlibs, this can results in
> unresolved symbols errors. That's why I wanna make sure only one libkolab is
> available for one distro.
> 
> For sure that means, that kdepimlibs must be built for libkolab.
> 
> Regads,
> 
> sandro

-- 
Sandro Knauß
Software Developer

Kolab Systems AG
Zürich, Switzerland

e: [email protected]
t: +41 43 501 66 91
w: http://kolabsys.com

pgp: CE81539E Sandro Knauß
_______________________________________________
devel mailing list
[email protected]
https://lists.kolab.org/mailman/listinfo/devel