[Pkg-giraffe-discuss] update from zarafa

[Mark Dufour]

hi guido,

finally, we updated the trademark policy on our site:

http://www.zarafa.com/content/zarafa-trademark-policy

in the meantime, we're hard at work on zarafa 7.2. a first beta is currently targeted for mid-november. at this point we will upload a tarball to our website, and I suggest you/we take this as a basis for packaging. hopefully also soon we will have a look at the remaining issues as listed on the giraffe ('zarafa'? :-)) wiki.


cheers,
mark.
 
 
-----Original message-----
> From:Mark Dufour <m.dufour at zarafa.com>
> Sent: Tuesday 30th September 2014 12:08
> To: Guido Günther <agx at sigxcpu.org>
> Cc: pkg-giraffe-discuss at lists.alioth.debian.org
> Subject: RE: [Pkg-giraffe-discuss] update from zarafa
> 
> hi guido,
> 
> thanks for your reply.
> 
> > Great news, Welcome aboard! Would you be interested to join the
> > pkg-giraffe alioth project to develop the packaging there or is there
> > any public git repo carrying 7.2 already?
> 
> I'm afraid we don't have a public repo at the moment. there should be a source tarball in the normal place once 7.2 (beta1) is released though. we are currently using a private SVN server, but are hoping to move towards GIT at some point, with all the AGPL3 code hopefully on a public server. this may take some time though..
> 
> I think the intention is to not share our own package files, but of course we are happy to try and help if you run into any problems or if something needs to be changed on our side.
> 
> > > 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).
> > 
> > Great!
> 
> actually we just  removed --with-system-gsoap and our bundled gsoap entirely, so always build against the system version. the desired gsoap prefix can now be set with --with-gsoap-prefix. so if testing does not show any problems, this is how it currently looks like it would work.
> 
> > > 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).
> > 
> > Great. Should this be packaged as a separate project?
> 
> I would say a 'zarafa-webapp' package within the current project would be fine..?
> 
> 
> cheers,
> mark.