Re: [Evolution] how to move mails and configs to a new machine

[Milan Crha <mcrha redhat com>]

On Thu, 2016-03-24 at 18:11 +0000, Pete Biggs wrote:
> > OK, I just tried this and I have to say WTF? How does anyone do
> > Evolution development anymore? I killed the processes and they don't
> > stay dead. What if I wanted to run a newly compiled version with a
> > debugger or command line flags or environment variables? I have to hack
> > DBUS files now? That's insane.
>
> Evolution itself doesn't restart, it's the backend processes. And it's
> not Evo that's starting them - it's things like Gnome-calendar that
> uses Evolution calendars as a source.  The way to deal with it if you
> are doing dev work is to kill the old process and start the new process
> in one command line - that way you start it before anything else has a
> chance to.

        Hi,
any client using the evolution-data-server data runs also the
background processes, thus it can be gnome-calendar, gnome-contacts,
bijiben and so on. It's usually gnome-shell-calendar-server restarting
the background processes for you under GNOME Shell. It's responsible to
show your events in the clock's calendar. Some other desktop
environments do not do this, thus it's easier to develop there.

The evolution-data-server D-Bus processes are run in a "replace" mode,
thus if you run them and its instance is already running, then the old
is stopped and is replaced by the new instance. Or should be, I do not
know, I do not run a desktop environment which restarts the evolution-
data-server background processes on its own after they are
stopped/crashed.
        Bye,
        Milan