GitLab

We don't deal with media art in tracker-extract since commit
6a050686 and ac84484d, mostly as it would require
us to weaken the tracker-extract sandbox.

We made a big compromise when splitting tracker core from tracker-miners
in that the common code that was needed by both parts would end up
duplicated. It's ugly but it works fine at the moment and allows us to
keep all of the common code private.

I had an issue when trying to embed tracker core into tracker-miners as
a Meson subproject though. Having two targets named tracker-common
caused confusion as duplicate targets aren't allowed, but they are not
quite equivalent so we can't just pick one or the other.

To work around this, I've renamed the copy in this repo to
tracker-miners-common. This only affects the target names, not the
actual function names.

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

This is the only setting read from extractor modules. It turns out
that under the right circumstances a g_settings_get_value() call
can trigger open() calls with readwrite permissions from the caller
thread. This is forbidden in extractor threads and triggers warnings
like:

dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user':
Permission denied.  dconf will not work properly.

Also, since this setting is meaningless to update during tracker-extract
lifetime, just drop the g_settings_bind() call, this means the setting
is only read once on startup.

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

Now we've removed the internal key file object, we've had to put in place
another method for supporting the existing TRACKER_USE_CONFIG_FILES
environment variable. Thanks to the GKeyfileSettingsBackend provided by
GLib, we can fallback to old school INI type config files for embedded
solutions or cases where we don't want dconf as a backend. This works rather
well.

IT should be noted, the INI files are *NOT* written out in full if they do not
exist, only options which are saved or different to the default settings are.
This is how it should be too.

Now we build man pages based on GSettings schemas using xsltproc with the
template in docs/manpages/gsettings.xsl. This is a useful aid when trying to
understand what config files can have in them. One thing it does highlight, is
the config documentation could be better :)

Migrated the KeyFile work in most apps to GSettings

Was causing unit tests to fail and made distcheck impossible

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

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

Allows all media/album art to be disabled with a setting of -1 or resized to a
width of choosing.

Based on the patch from Kiran Bhide <kiran.bhide@in.bosch.com>

The config option allows 3 states, 'always', 'first-index' or 'never'. The
default is 'first-index'.

The tracker-preferences dialog now has 3 radio buttons explaining this too.

This is a first attempt at fixing GB#659422

 * New max_bytes parameter added to tracker-extract config file. Extractors will
    read up to that configured limit.
 * Removed the need of reading the FTS config file from tracker-extract.
 * Word counting not done now in the extractors.

 Note: As a side-effect, last word extracted when reached max_bytes may get cut
  and only first chunk of it extracted.

This removes the following line:
/* -*- Mode: C; tab-width: 8; indent-tabs-mode: t; c-basic-offset: 8 -*- */

This is not needed and editors should work without this anyway.

tracker-config-manager is now tracker-config-file
tracker-config-utils is now tracker-keyfile-object

Now we have tracker-config-manager which is used to do all file based
operations for the config file. We also have tracker-config-utils
which does all the GKeyFile<-->GObject work for us. 

Perhaps these should be renamed at some point to:

  tracker-config-file
  tracker-object-keyfile

To be more aligned to what they actually do.

This also changes the way tracker-language.[ch] works.