GitLab

We only need /etc/passwd, not the whole thing.

This is a convenience helper only for super hackers.

In order to instantiate the Application class and test the toplevel
logic we need to be able to load the resource files. We can either
add custom hacks to py.test to find them in the /app director, or
use Meson as a wrapper that tells py.test where to find the files.

I have picked the Meson-as-a-wrapper approach since it will hopefully
be more robust.

If we don't set LC_ALL to a UTF8 locale, Python crashes the first time
it tries to write a non-ascii character to stdout or stderr.

This references the repository that contains the file, it causes
an infinite loop if we try to store the ref of the commit containing
that file in the commit whose ref we need to store ...

Otherwise the DConf GIO module is not loaded by subprocesses that
we launch, which prevents them interacting with DConf.

We currently launch `gsettings` as a subprocess from trackerappdomain
as a workaround for the issue that the GSettings API doesn't let us
manage multiple DConf profiles within a single process.

This also fixes an issue where we weren't actually using the Tracker
libraries from the install prefix. It seems to be impossible to make
these be picked up automatically as if we call
GIRepository.prepend_library_path() then all hell breaks loose.
Instead I updated the README with the correct magic env vars to use.

Everyone except developers will likely run Tagcloud via Flatpak in any
case as it is already a lot of work to build all the dependencies by
hand.

See README for context. We'll continue to default to using session-wide
Tracker services, but this option allows testing out new version of
Tracker without having to install stuff into /usr, and will also allow
running in a more restricted Flatpak sandbox.

Thanks to Alexandru for testing.

This allows building Tagcloud without having to manually build and
install patched versions of Gtk+ and such nonsense.