| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
This mirrors the miner D-Bus API that is already available.
https://bugzilla.gnome.org/show_bug.cgi?id=757369
|
|
|
|
|
| |
We don't expose it anywhere in API, may be hidden as an implementation
detail.
|
|
|
|
| |
And document the missing functions.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For a long time, all the Tracker extractors have manually constructed a
SPARQL update command using TrackerSparqlBuilder to represent their
output. This commit changes all of them to use the TrackerResource
class instead, which makes the code a lot more concise and readable.
This introduces some API breaks in the internal libtracker-extract
library. This has been a private library since Tracker 0.16 or earlier,
so it's fine.
If the extractors only output SPARQL then they are only useful to
people who are using a SPARQL store. Now we can output a serialization
format like Turtle as well. This will hopefully make the extract modules
useful outside of Tracker itself.
I've tried to preserve the behaviour of the extractors as much as
possible, but there are two things that are now handled differently:
* nao:Tag resources are given a fixed URI based on the tag label, such
as <urn:tag:My_Tag>. Previously they were inserted as blank nodes,
so tracker-store would give them unique IDs like <urn:uuid:1234...>
* All extractors created nco:Contact resources for content publishers,
but previously some would assign fixed URIs based on the name
<urn:contact:James%20Joyce>, while others would insert them as blank
nodes so they would be assigned unique IDs like <urn:uuid:1234...>.
Now, all extractors create nco:Contact resources with fixed URIs
based on the content creator's name.
https://bugzilla.gnome.org/show_bug.cgi?id=767472
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=767246
|
|
|
|
|
|
|
|
| |
This is based on the --set-log-verbosity option from `tracker daemon`.
The TRACKER_VERBOSITY environment variable also works here, and
overrides the value on the commandline, so I'm not sure if this patch
is really necessary...
|
|
|
|
|
| |
It now corresponds with the user-facing `tracker-extract` command,
rather than the hidden /usr/libexec/tracker-extract program.
|
|
|
|
|
|
|
|
|
|
|
|
| |
We're competing with gtk-doc.make here, which may turn out in
failures when doing mkdir on an already created directory, or
failures in writing xml/gtkdocentities.ent because we deleted
the directory under its feet.
So just do the same, use MKDIR_P to ensure it won't fail if
the directory is already there, and don't bother deleting it
as it's handled in gtk-doc.make. The ontology docs helper app
will rewrite the xml files anyway.
|
|
|
|
|
|
| |
It takes a file to be reset, works recursively for directories.
Immediately after reset, a reindex will be requested, so the data
is promptly indexed again.
|
|
|
|
|
|
| |
Gsettings are self-documenting, plus translatable. There is no need to
duplicate this documentation, and even less if it focuses on the
deprecated keyfile format. It is time to hide that under the rug.
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=751723
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=751724
|
|
|
|
|
| |
The devhelp index generation relies on specific roles set in the
docbook XML, we were setting none for ontology properties though.
|
|
|
|
| |
Otherwise it simply fails if there happens to be stale data
|
| |
|
|
|
|
|
|
| |
Those weren't that much clear nor useful, those are deleted in
a separate commit in case we want to rescue and rework them
someday.
|
|
|
|
|
| |
This is now unused, so remove the tool, and the configure.ac check
for fdp.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Ontology docs weren't in a much good shape, besides many ontologies
being seriously underdocumented (something which should improve
separately), the generated docs were little more than a data dump,
and the diagrams shown were broken, confusing, or both. This all
amounts to quite counter-productive developer docs.
So the ontology docs have been refurbished, the per-ontology
descriptions are still useful, but have been stripped of all images,
and the docs overall are now completely class-centric, per
rdfs:Resource subclass we now get:
- Ascii diagram of its local hierarchy, up to all its ancestors and
down to all its direct children.
- All properties that affect the specific class. This is notably
more intuitive now as there's properties defined on one ontology
that are in the domain of classes in another ontology, something
which you couldn't get at a glance in the previous docs
- It clearly states which properties supersede which superproperties,
which again makes it easier if those apply for the class at hand.
The result feels quite neater, and will indeed be more resembling
to other gtk-doc generated API docs.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Namespace has been cleaned up too, all APIs now start with:
TRACKER_PREFIX_
or
TRACKER_DATASOURCE_
The well known definition for the TrackerMinerFS graph has also been changed
to:
TRACKER_OWN_GRAPH_URN
because it now applies to more than just the TrackerMinerFS, we're using it
in:
tracker-writeback
tracker-miner-apps
tracker-miner-user-guides
...
libtracker-data
It should probably be internal actually.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 :)
|
| |
|
|
|
|
|
|
|
| |
Previously it took void and it was changed to take a GFile.
https://bugzilla.gnome.org/show_bug.cgi?id=737243
(cherry picked from commit 8c6485a312ffbd1c9bb3c95d5933284f56990045)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now we only show common RDF types by default, e.g. nfo:Document and it is
based on .rules file fallback types and some others specifically added.
There is also now a --all option to return all stats as was the behaviour
before.
In addition to this, the EXPRESSIONS provided on the command line following
the OPTIONS can be used to filter the stats, e.g. : 'tracker-stats doC' will
list the nfo:Document class and resources in the DB matching.
|
|
|
|
|
| |
This is a convenience function that retrieves the tracker:id for the
file nie:url and prepends it for processing.
|
|
|
|
|
|
|
|
|
|
| |
TrackerDataProvider
So now we have:
- TrackerEnumerator (GInterface)
- TrackerFileEnumerator (using GIO API)
- TrackerDataProvider (GInterface) which provides a TrackerEnumerator
- TrackerFileDataProvider (using GIO API) implemented as internal default
|
|
|
|
| |
Using environment variable: TRACKER_MINERS_DIR_DISABLED
|
|
|
|
|
|
|
|
|
| |
constructed()
This function gets the top level root for all roots, e.g. file:///
We also create the root nodes in constructed() not init() because then the
root GFile has been set in the properties when the object is initiated
|
| |
|
|
|
|
|
|
|
| |
tracker-miner-object.h
There is no need for these to be in a separate header and also they're useful
for other miners
|
| |
|
|
|
|
|
|
|
| |
Including:
- How we use it in TrackerMinerFS
- TrackerEnumerator itself
- TrackerFileEnumerator
|
| |
|
| |
|
|
|
|
|
| |
This only occurs during distcheck because the path is not relative any more,
but it should be referenced from $(top_srcdir) anyway to avoid these warnings.
|
| |
|
|
|
|
|
| |
This allows people to see updates in real time to the database for files and
any of the properties related to those.
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently all arguments supplied for --list are handled with an OR condition,
making the existing --or-operator redundant.
This makes --and-operator useful for querying for files matching 1 or more tag
labels.
https://bugzilla.gnome.org/show_bug.cgi?id=725717
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| | |
don't process
In normal circumstances, we may get TRACKER_DECORATOR_ERROR_{EMPTY|PAUSED},
but tracker-extract issues a g_warning(). We want to avoid using a warning for
these warnings because they're normal and expected operations.
|
|/
|
|
| |
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675198
|
|
|
|
|
|
|
| |
This has not been compiled or used in years and likely doesn't produce an
ontology compatible output that we could use.
EXTERMINATE!
|