| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
For historical reasons we have a codepath to build without full-text
search support, mostly useful on systems where the SQLite FTS5 module
is not available. This module is not difficult to build so in Tracker
3.0 we'll require it.
|
|
|
|
|
|
| |
This version (released on Oct 2016) added support for "row values"
(https://sqlite.org/rowvalue.html), which will be used for our MINUS
support, and possibly in other places of our SQL generation.
|
|
|
|
|
|
|
|
|
|
|
| |
Passing -Dbash_completion=false would error out as the
bash_completion_dir variable is never set.
meson.build:310:0: ERROR: Unknown variable "bash_completion_dir".
Fixes: d318ebeb5d4f984c61373b492d86ca50fbfd71dc
Closes: #187
|
|
|
|
| |
Fixes https://gitlab.gnome.org/GNOME/tracker-miners/issues/49
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit updates the functional tests in line with the
Tracker 3.0 architectural changes.
These tests used to spawn a private tracker-store daemon and communicate
over D-Bus. Most of the tests now create a local database in-process and
run tests against that, using the PyGObject bindings to drive
libtracker-sparql. It's good to test our Python bindings in this way.
Some tests also test connecting to a database over D-Bus. The 'fixtures'
module makes it easy to do either of these things.
The 08-unique-insertions test is gone, it claimed that "we can't test
tracker-miner-fs itself", but we can.
The 14-signals test is now a test of the TrackerNotifier API.
The 15-statistics test is removed as the API that it tests is gone.
Numbers were removed from the filenames of all tests.
It's debatable if the name "functional tests" really applies here any
more, perhaps a bigger distinction from the "unit tests" which also run
against libtracker-sparql is that these are written using Python and
PyGObject instead of C. In tracker-miners.git we will still be testing
multiple processes so the name will still make sense there.
|
| |
|
|
|
|
|
|
|
|
|
| |
These settings are no longer read through settings, at least from
library bits.
Since we no longer need the settings, we no longer need the schemas,
and we don't need the testsuite envvars to have things look into the
right gschema dirs, and we don't need to compile schemas either.
|
|
|
|
|
| |
We no longer need to merge C/Vala gir files, thus we no longer need
this script.
|
|
|
|
|
|
|
| |
This range of versions break ontology updates, in combination with
the newer technique to implement the union graph through WITH clause
queries. The previous and following working versions are 3.23.1 and
3.29.0.
|
|
|
|
|
|
|
| |
Nobody reads configure script summaries, make it sure they will by
spewing a build error. Make this overridable though, so people and
distributors at least make a conscious choice to shoot themselves
in the foot.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Meson 0.50.0 was released on 10th March 2019. We should
now be able to depend on it.
In particular, Freedesktop SDK now contains 0.51.0[1] so
this shouldn't break gnome-build-meta like last time (13948fda052e).
Fixes the following warnings:
WARNING: Project specifies a minimum meson_version '>=0.47' but uses features which were added in newer versions:
* 0.49.0: {'/ with string arguments'}
* 0.50.0: {'install arg in configure_file'}
1. https://gitlab.com/freedesktop-sdk/freedesktop-sdk/blob/master/elements%2Fcomponents%2Fmeson.bst
|
|
|
|
|
|
|
| |
The functionality that we were using from libuuid is now present in
GLib itself.
Fixes https://gitlab.gnome.org/GNOME/tracker/issues/131
|
|
|
|
|
|
|
| |
When building tracker-miners with -Dtracker:functional_tests=false
defined, it would fail with this error:
meson.build:64:2: ERROR: Requested variable "tracker_uninstalled_testutils_dir" not found.
|
|
|
|
|
|
|
|
| |
Meson provides a pkgconfig module to generate .pc files without any
need to defile stub files, but reusing libraries.
So just use this convenience feature instead of manually redefininig
variables and files.
|
|
|
|
| |
The 'master' branch is now for work leading towards Tracker 3.0.
|
|
|
|
|
| |
This is needed for the new 'run-uninstalled' script in
tracker-miners.git to run the correct version of the CLI.
|
|
|
|
|
|
|
|
|
| |
The tracker-miners tests now depend on the
tests/services/org.freedesktop.Tracker1.service file. We need to expose
it. The pkg-config variable is for situations where we build against an
installed Tracker core (so we use the normal service file, and honour
any custom location that the user specified for it). The Meson variable
is for when Tracker core is built as a subproject of tracker-miners.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of manually running and managing Tracker daemon processes
manually in the test, we now rely on our private D-Bus daemon to
do so.
This makes the test environment more like a real Tracker deployment.
Log output from the D-Bus daemon is now captured and output through
the Python logging system. This allows for finer-grained filtering
of output from the tests themselves and from the Tracker daemons.
Some test code is changed to support the new model.
|
| |
|
| |
|
| |
|
|
|
|
| |
Almost 2.3.0
|
|
|
|
|
| |
This fixes `ninja install`, which was broken since
aef285b4a801ba7e9d8c166.
|
|
|
|
|
|
|
|
| |
This isn't needed in the common case of distro package builds, as the
distro package will already provide a hook. However, our README.md
tells developers to install into a prefix like ~/opt/tracker, and
that is broken by default because GLib will complain that none of the
settings schemas are installed.
|
|
|
|
|
|
|
|
| |
This fixes the case where Tracker is installed into a non-standard
prefix such as /opt/tracker and then fails to start with an error
such as this:
/opt/tracker/bin/tracker: error while loading shared libraries: libtracker-control-2.0.so.0: cannot open shared object file: No such file or directory
|
|
|
|
|
|
|
| |
Run dbus-run-session with the --config-file parameter in order to allow to run
tests without installing tracker before.
Closes: https://gitlab.gnome.org/GNOME/tracker/issues/24
|
|
|
|
| |
API additions for the 2.3 series are now possible.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 17777040c63b7bc8586fa77bfa1219c0d96a9dd9.
Some projects that include Tracker haven't yet updated to Meson 0.50. This
change broke gnome-build-meta for example:
https://gitlab.gnome.org/GNOME/gnome-build-meta/-/jobs/286671
The install: arg isn't actually required as for configure_file() targets
Meson will infer whether an install is needed by the presence of the
install_dir: arg.
|
|
|
|
|
|
|
| |
Meson helpfully warns us that this is needed:
WARNING: Project specifies a minimum meson_version '>=0.47' but uses features which were added in newer versions:
* 0.50.0: {'install arg in configure_file'}
|
| |
|
|
|
|
|
| |
Allows distros that are cross compiling to tell tracker whether
sqlite3 has FTS support builtin or not.
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
The main use case for the docs option seems to be to not spend time on
gtk-doc generation. It is rather unexpected this also disables the
installation of manpages, which are just installed as-is with no work
involved.
|
|\ \ |
|
| | |
| | |
| | |
| | | |
An oversight of the meson port.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
build: Raise glib dep to 2.46.0
See merge request GNOME/tracker!57
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
It used to be 2.44.0 in configure.ac, and the code does use at least
g_strv_contains, which is new in 2.44.
It now also uses g_async_queue_push_front_unlocked and
g_settings_schema_list_keys, which are new in 2.46.
|
|/ / |
|
| |
| |
| |
| |
| |
| | |
For the lulz, releng all over the place crapped out with the "new"
versioning. This is just a tag, and does not get a tarball in
gnome FTP.
|
|/
|
|
|
|
|
|
|
| |
Allow running tests without the need to install the gsettings schemas.
This commit moves all the gschemas in the data directory and compiles
them in the build directory. Tests that require gschemas need to be
launched with the proper GSETTINGS_SCHEMA_DIR env variable.
Fixes: https://gitlab.gnome.org/GNOME/tracker/issues/60
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
The previous change did not leave the expected .0 symlinks.
'soversion' is the actual version linked against. To match the scheme
used by libtool, we need to give the libraries a 'version' as well.
|
|/
|
|
|
|
|
| |
Export those in tracker-sparql.pc, so users may find out the install
details.
Related: https://gitlab.gnome.org/GNOME/tracker-miners/issues/19
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This warning is disabled by default at warning level 1.
Multiple distros are building Tracker with -Werror=format-security and
discovering regressions, we have had reports from Debian, Fedora and
NixOS so far, so let's enable it by default.
|
| |
| |
| |
| |
| |
| | |
The scheme adopted for development releases is "alphaN" for unstable
releases, and "betaN" for release candidates. major/minor/micro version
stay fixed in the targeted version.
|
| |
| |
| |
| |
| |
| | |
Leaving to '0' is not enough if several versions of the library are
installed (say, in different prefixes). Add back the library soversion,
similarly to how it was done in autotools.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Following https://www.bassi.io/articles/2018/03/15/pkg-config-and-paths/,
this includes dbus service, bash completion, gir and typelib paths.
Unfortunately, the path for systemd user units cannot be overriden, so
use a path made from our libdir path.
This allows for trouble free builds by just defining prefix. If installing
onto system paths was desirable on some setups, it might return through a
-Duse_system_paths boolean build option that disables the overrides, but
this is a preferrable default.
|