| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| | |
docs: Clean up some errors in libtracker-sparql-doc build
See merge request GNOME/tracker!82
|
| |
| |
| |
| |
| | |
This function was removed in 8acaa3e77283efd2a5661ac0ae050b8993c8e08b
but some corners of the documentation didn't yet get the message.
|
|\ \
| |/
|/|
| |
| | |
Fix warnings and broken links in libtracker-miner-doc build
See merge request GNOME/tracker!79
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The libtracker-miner library depends on libtracker-sparql and uses some
of the types defined there. The docs refer to these types, which
previously produced warnings and broken links:
html/TrackerDecorator.html:739: warning: no link for: "TrackerSparqlBuilder" -> (<span class="type">TrackerSparqlBuilder</span>).
html/TrackerMiner.html:124: warning: no link for: "TrackerSparqlConnection" -> (<span class="type">TrackerSparqlConnection</span>).
html/TrackerMiner.html:655: warning: no link for: "tracker-sparql-connection-get" -> (<code class="function">tracker_sparql_connection_get()</code>).
With this change, the warnings are gone and the links to types from
libtracker-sparql work as expected.
|
| |
| |
| |
| |
| |
| | |
This fixes the following warning:
html/TrackerMinerFS.html:1238: warning: no link for: "api-index-1.8" -> (1.8).
|
|/
|
|
| |
Still not fixed the Tracker 2.0 references here and there
|
| |
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Fixes: https://gitlab.gnome.org/GNOME/tracker/issues/66
|
| |
|
|
|
|
| |
This isn't even used, but that's no reason to leave it out of docs.
|
|
|
|
|
| |
There were also some references to no longer existing ontology, that's
been wiped out.
|
|
|
|
|
| |
That is as much as we say about them, gets rid of warnings during docs
generation.
|
|
|
|
| |
The build_always option is deprecated since meson 0.38.0
|
|
|
|
| |
So we get proper links to glib types.
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently Tracker domain rules must be installed inside Tracker's data
directory (usually /usr/share/tracker). This is limiting as it means
only system packages can add them. A program installed into /opt is
unable to use a custom domain, for example. Since Tracker is implemented
as a system of daemons, it's not particularly straight forward to work
around this by setting XDG_DATA_DIRS= to point somewhere non-standard
either.
This patch removes this restriction in a simple way: it allows users to
pass a full path to the domain rule, rather than just the base name.
|
|
|
|
|
| |
This also adds `tracker extract -o json` to dump resources in JSON-LD,
in anticipation of corresponding updates in tracker-miners.git.
|
|
|
|
|
| |
Add missing example files to content, and generate ontology
docs for the builtin ontology bits.
|
|
|
|
|
| |
Using absolute paths breaks if we are embedded as a subproject because
the toplevel path is that of the toplevel project.
|
|
|
|
|
| |
We should maybe reword this to not include the API version, but I can't
see a simple way right now.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=787246
|
|
|
|
|
| |
These manpages persist on the tracker-miners module, they can be removed
from this repo.
|
|
|
|
| |
Missing comma.
|
| |
|
|
|
|
| |
This was not added on git.
|
| |
|
|
|
|
|
| |
Fixes some duplicate reference warnings when building libtracker-sparql
docs.
|
| |
|
| |
|
|
|
|
|
| |
Remove no longer existing methods, add the newer objects/methods
that were missing, and add some further docs here and there.
|
|
|
|
|
| |
The newer methods were still missing from API docs, add them
in the respective sections.
|
|
|
|
|
| |
These functions need to be avoided so that Tracker doesn't break when
included via subproject() into another Meson project.
|
|
|
|
| |
This is being split to its own package
|
|
|
|
| |
It is now defined globally, so can removed from specific targets.
|
|
|
|
|
|
| |
This is implemented on direct connections and the generic backend. The
TrackerNamespaceManager will be filled in from the internal ontologies, as
read by the TrackerDataManager.
|
|
|
|
|
|
|
| |
Just add tracker_decorator_info_complete[_error] functions to let the
decorator implementation give back the resulting SPARQL. This way the
TrackerDecorator API is agnostic of the method/API used to build the
SPARQL.
|
|
|
|
|
| |
These are C helper functions, so users may create trees of TrackerResources
without having to manually unref all non-root ones.
|
| |
|
|
|
|
|
|
| |
Those functions have been deprecated for years and are being removed
for 2.0. Use tracker_sparql_connection_get() and async variants instead,
that will smartly use the direct connection underneath.
|
|
|
|
|
|
|
|
|
|
|
| |
This is a pretty pointless shallow wrapper to GFileEnumerator. Just make
TrackerDataProvider offer GFileEnumerators. If anyone ever was in need for
implementing a TrackerEnumerator, they can do the very same by implementing
GFileEnumerator, and handing those from their TrackerDataProvider impl.
This also cuts a level of indirection in directory crawling (i.e. no
wrapping of GTasks in GTasks), and allows us to fully use GFileEnumerator
API (eg. g_file_enumerator_next_files will be handy).
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It was cool when Tracker search was barely integrated anywhere.
Nowadays, it's nothing but an aging showcase app (eg. was conceived
in the gtk2 days and barely ported to gtk3, and it shows everywhere).
If you want a modern and capable search UI, try Nautilus. If you
are outraged that tracker-needle is gone and ended up here, by all
means be my guest, reset to the parent of this commit and take it
out of tree. If you join #tracker I'll gladly give you advise on
how could it be brought up-to-date. But our hands are full, sorry,
we leave cool UIs to others.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a mix of store and miner features which can't be assumed to go
together. It is better to leave configuration UI up to the environment,
in the GNOME case this is gnome-control-center search panel.
For settings that fall in the cracks, or for environments that don't
integrate Tracker search in their configuration UI, there's the rather
capable dconf-editor which will provide all toggles, and will explain
them better than any UI we may have.
In the future the CLI tools might gain some configuration subcommand,
but it will not be a graphical UI.
|
|
|
|
|
|
| |
The only user that might ever care does already implement it itself.
There is no need to provide this infrastructure that will be scarcely
used in libtracker-miner API.
|
|
|
|
|
|
| |
These were supposedly added for testing, but they are not used
anywhere, nor it sounds ok to fundamentally change TrackerMinerManager
behavior. Let's remove these.
|
|
|
|
|
|
|
| |
Only check_file() remains, with an extra priority argument. The default
G_PRIORITY_HIGH in the older check_file() was unintuitive, and is now
explicitly specified in the org.freedesktop.Tracker1.Miner.Files.Index
interface calls.
|
|
|
|
|
| |
More unused API that is a thin wrapper to TrackerIndexingTree, just
remove it.
|
|
|
|
|
|
|
| |
The whole set of tracker_miner_fs_add_directory_without_parent(),
tracker_miner_fs_directory_add(), directory_remove() and
directory_remove_full() are all covered by TrackerIndexingTree and
basically unused, except for code in examples/.
|