GitLab

Thus it can be used to influence where the needed libraries are
looked for from the outside.

The only two parts using it were GDBus objects for address book and
calendar view, which could be easily transformed to use gdbus-codegen,
the same as the rest of the GDBus objects defined in src/private/.

Related to GNOME/evolution#113

Closes GNOME/evolution-data-server#52

Closes GNOME/evolution-data-server#41

Closes GNOME/evolution-data-server#51

(cherry picked from commit 37e582ad)

Similar to GNOME/evolution#196
when intltool-merge is called in parallel, it could either rewrite
the ongoing attempt to build it or use an incomplete data, which
results in broken output files (.desktop, .metainfo and so on).
This change ensures the intltool-merge cache is created only once
and any other requests which would use it will wait until it's created.

Related to GNOME/evolution#196

Related to https://bugzilla.gnome.org/show_bug.cgi?id=658742

When there had been two requests to download one message at the same time
the later waits for the former to finish, then it reads the message
from the local cache. The problem is that the later can use the same
stream as the former, but this stream is re-winded at the end, thus
the later attempt doesn't read anything and produces basically empty
message, instead of the proper content.

This could be sometimes observed when viewing message source of
a message which was not downloaded yet.

Closes GNOME/evolution-data-server#49

Closes GNOME/evolution-data-server#50

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

Closes GNOME/evolution-data-server#48

There had been logged only headers even when the user requested to
log everything due to use of SoupRequest. The added code logs also
the response body when requested. The order of the headers and
the body can be opposite, due to libsoup internals.

When the test creates a new ESource and saves it, then it waits
for an "source-added" signal on an ESourceRegistry instance to know
that it had been "registered" in the registry. It could sometimes
happen that the client received this signal before the factory,
which means that trying to open this ESource fails with a NOT_FOUND
error due to the factory's ESourceRegistry instance wasn't updated yet.
This change tries again for three times with a one second delay, which
should be enough to have the factory's list of known sources updated.

Do not localize a config entry text which is an empty string, because
localizing empty string means getting information about the localization
itself.

Otherwise the CamelSettings are not properly used. This had been
caused by the changes from the previous commit.

Also introduce and use e_util_strcmp0(), which can avoid the most common mistake
of comparing a NULL with an empty string, which are equal after e_util_strdup_strip(),
but which caused a false property change notification.

Closes GNOME/evolution-data-server#44

Closes GNOME/evolution-data-server#43

Closes GNOME/evolution-data-server#42

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

Related to GNOME/evolution-data-server#40

Closes GNOME/evolution-data-server#40

When an interface contains a D-Bus subtree, then proxy it too, thus
the caller has available everything the interface provides.

Closes GNOME/evolution-data-server#38

Closes GNOME/evolution-data-server#37