Bug#404942: syncevolution packaging update
On Tue, 2009-08-04 at 22:04 -0300, David Bremner wrote:
> So I have debian packaging for syncevolution 0.9beta3+something at
>
> Vcs-Git: git://git.debian.org/git/collab-maint/syncevolution
> Vcs-Browser: http://git.debian.org/?p=collab-maint/syncevolution
>
> It is integrated with upstream history from moblin. The main question
> mark is the embedded copy of libsynthesis.
>
> I have a few questions for Patrick
>
> 1) can I assume that the version of synthesis embedded is given by the git hash in src/synthesis/README?
> So if I just check that hash out, I'll get the same code?
Yes.
> 2) Paul Liu suggests making separate packages for the syncevolution shared libraries so that applications
> can link to them. Is the ABI stable enough (i.e. say over a few releases) to make this worthwhile?
No, not at all. The ABI exposes internal C++ classes (inherited from
using the Funambol library), which makes it hard to keep it stable.
Right now there are no apps outside of our own source tree which need
the libs either, which minimizes the need for a stable ABI.
I intend to rewrite the backend API, and this time will be more careful
to keep it stable.
> 3) Same question for libsynthesis. I saw there have been no tarball
> releases yet, which makes me think things are still prety fluid.
With libsynthesis there are still changes going in, in particular right
now where I make changes while Synthesis is effectively in summer
vacation and can't merge them back.
However, libsynthesis in general has a very stable API and ABI, so it
would make sense to package it separately.
Can you package it directly from git, based on a tag? Synthesis most
likely will not produce traditional .tar.gz archives that often. In
SyncEvolution I prefer to avoid doing that myself by bundling the
source.
--
Bye, Patrick Ohly
--
Patrick.Ohly@gmx.de
http://www.estamos.de/
Reply to: