Tracker is the file indexing and search provider used in the GNOME desktop environment.
This package is known to build and work properly using an LFS 12.0 platform.
Download (HTTP): https://download.gnome.org/sources/tracker/3.5/tracker-3.5.3.tar.xz
Download (FTP): ftp://ftp.acc.umu.se/pub/gnome/sources/tracker/3.5/tracker-3.5.3.tar.xz
Download MD5 sum: f78a0d145007d9871174be21a49ce9ef
Download size: 2.5 MB
Estimated disk space required: 51 MB (with tests)
Estimated build time: 0.3 SBU (with tests)
JSON-GLib-1.6.6, libseccomp-2.5.4, and Vala-0.56.11
gobject-introspection-1.76.1, ICU-73.2, libsoup-3.4.2, PyGObject-3.44.1, SQLite-3.42.0, and tracker-miners-3.5.2 (runtime)
asciidoc-10.2.0, Graphviz-8.1.0, libsoup-2.74.3, bash-completion, and libstemmer
Fix the location to install the documentation into:
mv docs/reference/libtracker-sparql/doc/{Tracker-3.0,tracker-3.5.3} &&
sed '/docs_name/s/Tracker-3.0/tracker-3.5.3/' \
-i docs/reference/libtracker-sparql/meson.build
Install Tracker by running the following commands:
mkdir build &&
cd build &&
meson setup --prefix=/usr \
--buildtype=release \
-Dman=false \
-Dsystemd_user_services=false \
.. &&
ninja
Now, as the root user:
ninja install
To test the results, issue: meson
configure -Ddebug=true && ninja test. The
test suite should be run from a graphical session. One test,
tracker: fts / fts, is known to fail
due to an incompatibility with SQLite-3.42.
--buildtype=release:
Specify a buildtype suitable for stable releases of the package, as
the default may produce unoptimized binaries.
-Dman=false: This switch
prevents the build process from generating man pages. Omit this
switch if you have asciidoc-10.2.0 installed and wish to
generate and install the man pages.
-Dsystemd_user_services=false: This
switch prevents the build process from installing systemd user
services since they are useless on SysV systems.
meson configure -Ddebug=true: This command enables some debug checks necessary for the test suite. We don't want to enable them for the installed Tracker 3 libraries and programs, so we run the test suite after installation.