| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This object allows exporting a sparql connection at a given DBus connection
and object path.
|
| |
|
|
|
|
| |
This will be used when we support graphs for real.
|
|
|
|
|
|
|
|
|
|
|
| |
According to https://www.w3.org/TR/sparql11-query/#grammarEscapes,
double and single quotes may be escaped regardless of the type of
string literal we are dealing with.
We should make tracker_sparql_escape_string() match accordingly.
Related: https://gitlab.gnome.org/GNOME/nautilus/issues/163
https://gitlab.gnome.org/GNOME/nautilus/merge_requests/456
|
| |
|
|
|
|
|
|
|
|
| |
Just because we changed a property, does not mean we should delete the
old value of that property, because it might still be in use somewhere
else.
See https://gitlab.gnome.org/GNOME/tracker/issues/127
|
|
|
|
|
|
|
| |
TrackerResource may in some circumstances contain links to itself, or other
reference cycles. We should eventually offer a destroy() method, but
implementing dispose() will at least provide a tool to ensure those cycles
are gone.
|
| |
|
|
|
|
|
|
| |
Fixes this warning:
../../tracker/src/libtracker-sparql/tracker-namespace-manager.c:335: Warning: Tracker_C: tracker_namespace_manager_foreach: argument func: Missing (scope) annotation for callback without GDestroyNotify (valid: call, async)
|
|
|
|
|
|
|
|
|
| |
Hopefully the last chapter in the "make libtracker-common static" saga...
Turn this object into a refcounted struct, as we still may end up with
multiple copies of libtracker-common in libtracker-miner, through
libtracker-sparql.so and directly as it also uses libtracker-common.
This resulted in assertions when trying to register the same type name
twice.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We were using 'link_with: libtracker-common' to link to
libtracker-common in some places, which worked around an old Meson bug.
The bug (https://github.com/mesonbuild/meson/issues/671) was fixed in
Meson 0.42 so we can now remove the workaround.
The advantage of using 'dependency: tracker_common_dep' is that
transitive dependencies are now automatically propagated. We now
probably have some redundant dependency information on some of the
libraries, but that isn't a problem.
Fixes https://gitlab.gnome.org/GNOME/tracker/issues/112
|
|
|
|
|
|
|
|
|
|
|
| |
We need to express this dependency, otherwise the C code might fail to
build with this kind of error:
../src/libtracker-sparql/tracker-notifier.c:89:10: fatal error: tracker-generated-no-checks.h: No such file or directory
The `tracker-generated-no-checks.h` file is generated by Vala.
Hopefully fixes https://gitlab.gnome.org/GNOME/tracker/issues/96
|
|\
| |
| |
| |
| | |
docs: Clean up some errors in libtracker-sparql-doc build
See merge request GNOME/tracker!82
|
| |
| |
| |
| |
| |
| | |
This fixes the following warning while building the docs:
html/TrackerNotifier.html:363: warning: no link for: "Audio" -> (<span class="type">Audio</span>).
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It turns out that json-glib only allows signed integer fields. This
fixes missing values when running `tracker-extract -o json-ld` in
certain cases. If you hit this bug you might also see the following
error:
Invalid value of type 'guint'
|
|/
|
|
|
|
|
|
|
|
|
| |
We do keep a notion of already visited TrackerResources when generating the
output. However that could go wrong if the TrackerResource references itself
or a "parent" TrackerResource.
Add the resources to the done list beforehand, so they are ensured not to be
visited again if such backreferences exist.
Related: https://gitlab.gnome.org/GNOME/tracker-miners/issues/60
|
|
|
|
| |
Still not fixed the Tracker 2.0 references here and there
|
|\ |
|
| |
| |
| |
| | |
An oversight of the meson port.
|
|/
|
|
|
|
|
|
|
|
|
|
| |
We don't need to store the full path build filename
in comments in the header files.
This change was recommended by the Reproducible Builds
project.
https://reproducible-builds.org/
https://bugs.debian.org/915503
|
|
|
|
|
| |
This object can hold a long lived query, in which parameters may be changed
prior to execution.
|
| |
|
|
|
|
|
|
|
| |
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 reverts commit 20b9f3673d16d07070619cb0ff770d0dabbcc74c.
Gnome infrastructures should already have meson >= 0.48.0, let's give it
another try.
|
|
|
|
|
|
| |
We generate that file ourselves, so configure_file() is unneeded as the
file requires no substitutions. Fixes a warning on recent meson, as the
configuration should not be empty.
|
|
|
|
|
|
|
|
|
| |
The docs were not going through gtkdoc-scangobj, and the libtracker-sparql
docs were just looking in source dir while it should also look for gtk-doc
comments in generated files from vala.
Now that we're there, use include_directories() to get rid of relative
paths.
|
|
|
|
|
|
|
|
|
| |
Works with meson 0.48.0, but not with the versions in CI/build.gnome.org.
Not cool, meson. We'll have to linger with broken internal library
dependencies till I restructure the src/libtracker-* mess, or 0.48.0 gets
old.
This reverts commit 6799d903e9767288b10b02e1f362e040a02f69ed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Even though libtracker-data uses types from libtracker-sparql, this
is the wrong way around. However, doing the right thing here still
breaks because meson is playing smart here and passes --no-undefined
for every shared library by default, so build breaks with obviously
undefined symbols.
Correct the dependency tree to be exactly how it was with autotools,
and override b_lundef when building libtracker-data to leave the
borrowed symbols undefined. The gaps will be filled in because
everyone must link with libtracker-sparql.
Closes: https://gitlab.gnome.org/GNOME/tracker/issues/44
|
|
|
|
|
|
|
| |
tracker_notifier_finalize() may accidentally stumble upon a null pointer
or two, throwing warnings and making Nautilus CI pipelines fail.
Related: https://gitlab.gnome.org/GNOME/tracker/issues/43
|
| |
|
|
|
|
|
|
| |
This reverts commit df768eff07c817924f431ece0d09a24edab74de2.
Now that we branched for tracker-2.2, reintroduce this new API.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This reverts commit eb24ea93bc550934d15223d002b490143e604921.
This is an interesting feature, but not a good timing. Punt for
2.2.x that will happen after 3.30.
|
|
|
|
|
| |
The separator being optional is a tracker-specific "feature". Seems better
to use proper SPARQL1.1 here.
|
|\
| |
| |
| | |
See https://gitlab.gnome.org/GNOME/tracker/merge_requests/14
|
| |
| |
| |
| |
| |
| |
| |
| | |
This header was unusable from C++ code as 'namespace' is a reserved
keyword there.
Based on a patch by Santtu Lakkala from
https://bugzilla.gnome.org/show_bug.cgi?id=791510
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We should be consistent about what the name of a Tracker domain actually
is. In the domain rule we specify Domain=org.freedesktop (for the
default rule) or Domain=org.example.App (for a custom domain). But
internally tracker_domain_ontology_get_domain() would return
org.freedesktop.Tracker1 or org.example.App.Tracker1, i.e. the domain
name now has '.Tracker1' appended.
This does make sense in most cases, but it means there's no way to get
the actual name of the domain from a TrackerDomainOntology object. This
commit changes the existing function to not append '.Tracker1' in the
value it returns, which means that function can now be used to get the
base name of the domain. The assumption is that callers are normally
appending stuff to this base name anyway so it's not much extra effect
to also append the '.Tracker1' component if needed.
libtracker-common is internal to Tracker so this doesn't constitute a
public API break.
|
|\ \
| | |
| | |
| | | |
See https://gitlab.gnome.org/GNOME/tracker/merge_requests/14
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently it's only possible to open a TrackerSparqlConnection to
an instance of Tracker that is running on the session-wide message bus.
There are use cases for running the Tracker daemons on a private
session bus though. In fact it's necessary to do this if you want to
set up a custom domain without having to become root and create .service
files in /usr/share/dbus-1/services. It would also be useful for the
functional-tests to be able to use libtracker-sparql instead of having
to talk directly to Tracker's D-Bus API.
|
|/
|
|
|
|
|
|
| |
This header was unusable from C++ code as 'namespace' is a reserved
keyword there.
Based on a patch by Santtu Lakkala from
https://bugzilla.gnome.org/show_bug.cgi?id=791510
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Creating a single query for all values to delete can only work if
all values have a match. As soon as a value is already missing,
the query would just bail out as there's no real match.
We want to delete every value individually regardless of other
properties, so decompose the single delete into multiple individual
deletes.
Fixes "Unable to insert multiple values for subject..." warnings
as the insertion queries would rely on single-valued properties being
cleared beforehand.
https://gitlab.gnome.org/GNOME/tracker/issues/28
Closes: #28
|
|
|
|
|
| |
This also adds `tracker extract -o json` to dump resources in JSON-LD,
in anticipation of corresponding updates in tracker-miners.git.
|
|
|
|
|
|
|
|
|
|
| |
This script dates from a long time ago when Meson lacked ways to install
generated headers.
This fixes an issue where `ninja install` in tracker.git triggers a
rebuild of lots of stuff from tracker-miners.git, which happened because
the mtime of the installed generated headers would become newer than the
build files in tracker-miners.git and cause ninja to rebuild them all.
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=792691
|
|
|
|
|
|
|
|
| |
The GVariant type string "i" refers to a signed 32-bit integer.
Therefore, gint32 is a much safer bet than gint, whose size is not
guaranteed across all platforms.
https://bugzilla.gnome.org/show_bug.cgi?id=792301
|
|
|
|
| |
The tracker_notifier_new() function allows NULL for 'classes'.
|
|
|
|
| |
The 'classes' parameter wasn't annotated correctly.
|