This happens in normal operation, we don't need to announce it.

Developers wanting to trace things relating to DBus names can use
tools like gdbus monitor or d-feet.

https://bugzilla.gnome.org/show_bug.cgi?id=712841

This allows one to run the EDS processes in relocated XDG user data
directories, without the registry stealing your user data from ~/.evolution
or previous versions.

Currently we log a message every time the migrater starts, even
if we have nothing to migrate.  This clutters the systemd journal.

To fix this cleanly, rework this code so that error handling is
cleaner and more unified, which preserves the migration context.

The gsettings schemas need to all be stored and installed from the data/
directory, this is because we compile them locally in-tree and set the
GSETTINGS_SCHEMA_DIR to a local directory in order to run our tests
at make check time (tests dont work without this, instead GSettings wants
to abort for a missing schema).

Check for and parse a ~/.gconf/%gconf-tree.xml file during migration.
This is mainly for Debian, which I think accidentally merged some users'
GConf trees at some point.

This also adds a command-line program (evolution-scan-gconf-tree-xml),
which parses an arbitrary %gconf-tree.xml file as a recovery measure.

Populate a ~/.config/evolution/sources/system-proxy.source file from
the old "org.gnome.evolution.shell.network-config" schema on startup,
and tag the schema keys as deprecated in their description fields.

This represents the default proxy profile in E-D-S.  New accounts will
automatically reference this proxy profile.  Additional proxy profiles
can be defined as needed for particular accounts.

g_type_init() is deprecated in GLib 2.36.

This commit avoids initializing GTK+ in a 'make check' environment,
as well as avoiding printing of any non-critical messages from
the services running in a 'make check' environment.