Re: Continuous Builds in GNOME

[Milan Crha <mcrha redhat com>]

On Mon, 2016-06-06 at 22:21 +0200, Sébastien Wilmet wrote:
> On Mon, Jun 06, 2016 at 10:10:58PM +0200, Sébastien Wilmet wrote:
> > There is a solution: bump the major version of Camel or EDS each time an
> > API or ABI break is unavoidable, making the new major version
> > parallel-installable with the previous ones. And that, every 6 months if
> > needed (or one year if the development cycle is longer for the
> > Evolution-related projects).

        Hi,
there is no need to give me pointers to things and practices which are
already used in the project. It can be useful for some other projects,
for some maintainers following this thread, thought.

I mean, that's exactly what we do (unless accidentally overlooked). If
the API/ABI changes, a soname version is bumped for that respective
part, at least once between releases (I just did a soname version bump
of Camel for 3.21.3 in one commit, then I did another change in the
Camel API in another commit, but I didn't bump the soname version,
because that all will be available for the early adopters in one single
release, 3.21.3).

> Mmh maybe it's not possible for EDS, since it's a daemon (or contains
> a daemon) and thus only one instance can run on a system. I don't
> know much about how EDS, Camel etc are designed.

The Camel is a library, which happens to be part of the evolution-data-
server. The evolution-data-server consist also of some D-Bus services,
which allow clients to connect to them and have address books and
calendars, tasks, memos. The Camel library is used for Mail and it
doesn't provide any such D-Bus service as of today. The D-Bus services
are also versioned, thus, if needed, the version can be bumped.

Nonetheless, the evolution-data-server doesn't support parallel builds
into the same prefix, neither the evolution.

We diverged from the initial thread topic a bit here, I'm afraid.
        Bye,
        Milan