[Pkg-giraffe-discuss] update from zarafa

Mark Dufour m.dufour at zarafa.com
Tue Sep 23 13:48:54 UTC 2014


hi all,

 
on behalf of several other developers and myself at zarafa, I am happy to announce that (after some private communication) we would like to actively help out (again?) getting zarafa properly packaged in debian. over the past year there have been two important developments inside zarafa in this regard:

 
1) we have been working on separating out libgsoap, which since times ancient has been statically linked into zarafa (version 2.7.13 if I'm not mistaken). it looks like for the 7.2 release we can finally get rid of this (new configure option: --with-system-gsoap).

 
2) in part triggered by your rebranding effort, we have been working on a new and improved trademark license based on that of libreoffice, which ideally would mean that no debranding is necessary. not for the name and not for the logos. 

 
also, webaccess is not being developed anymore by now, and probably will be removed as of 7.2. some of the issues mentioned on the wiki have probably already been solved in its successor webapp (the .swf file, and the fsckeditor are gone at least).

 
we hope to give you the chance to review our new trademark license shortly.

 
for now we would like to have a conversation about the issues on the wiki that would still need to be solved. I'd like to start with the dlopen issue. we're moving libraries around quite a bit for the 7.2 release already, so perhaps we can easily solve this right away.

 
so for the user plugins, it seems easy. we just move them somewhere outside of /usr/lib, right? (they are now in /usr/lib/zarafa.) where would they ideally by located? as for the rest, I think there are only libzarafaclient.so and libzarafacontacts.so remaining. as these are probably always opened using dlopen via libmapi.so, I think it wouldn't hurt to move them into the same dir as the plugins. would this solve the issue for you?

 
as for libvmime and libical, is there anything left to do if our intention is for zarafa to work with the debian-provided versions of these? I would consider it a bug if we are dependant on a patched version of either.

 
 
 
again on behalf of the development team at zarafa,

mark dufour. 

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-giraffe-discuss/attachments/20140923/240495f5/attachment.html>


More information about the Pkg-giraffe-discuss mailing list