- Jun 29, 2017
-
-
Carlos Garnacho authored
This can only be used if the default domain ontology file is not found, and is now used on tests that do rely on the default tracker-store instance. Also, add back the TRACKER_DB_ONTOLOGIES_DIR, under the same restrictions.
-
Carlos Garnacho authored
So it can be specified from the miner.
-
Carlos Garnacho authored
Better than calling the pragma and involving prepared statements
-
Carlos Garnacho authored
It does not matter much since the getter still returns a sunk reference, but better to be consistent with the real implementation.
-
Carlos Garnacho authored
This will make the miners not specified in the domain ontology description file invisible from the API user perspective.
-
Carlos Garnacho authored
So it still behaves as it used to do.
-
Carlos Garnacho authored
This is purely a hint, and people may still run things manually or perform updates against this domain ontology themselves. Will be useful so we don't autostart more miners than necessary through the libtracker-control API.
-
Carlos Garnacho authored
We do already deal with ontology locations at this point, which we also print.
-
Carlos Garnacho authored
Pass the TrackerDataManager down tracker_backup_save(), so we can fetch the DB file underneath.
-
Carlos Garnacho authored
And exit as soon as the name vanishes. It may safely continue its operations on the next startup.
-
Carlos Garnacho authored
And exit as soon as the name vanishes. It may safely continue its operations on the next startup.
-
Carlos Garnacho authored
And exit as soon as the name vanishes. It may safely continue its operations on the next startup.
-
Carlos Garnacho authored
And exit as soon as the name vanishes. It may safely continue its operations on the next startup.
-
Carlos Garnacho authored
Tracker-store will wait till there are no elements left before exiting, in order to ensure it does so cleanly.
-
Carlos Garnacho authored
Use the domain name to find out the right tracker-store DBus name.
-
Carlos Garnacho authored
-
Carlos Garnacho authored
This should be ported to TrackerNotifier, which already does the right thing.
-
Carlos Garnacho authored
Otherwise the database might not be created yet when creating the direct connection.
-
Carlos Garnacho authored
-
Carlos Garnacho authored
I personally prefer using the excuse of the major version bump than adding a tracker_miner_manager_new_fuller() variant, as this is clearly a construct_only thing. Creating a TrackerMinerManager with an specific domain will allow dealing with the miners spawned for it.
-
Carlos Garnacho authored
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.
-
Carlos Garnacho authored
This will be used by TrackerMinerManager in order to find out the right dbus names according to the domain ontology.
-
Carlos Garnacho authored
Because we're registering 2 interfaces and 2 dbus names, both expose the same 2 interfaces and are introspectable the same way. This makes no sense, just use the org.freedesktop.Tracker1.Miner.Files name for both interfaces.
-
Carlos Garnacho authored
So it is possible to use TrackerMiner facilities in-process using a dedicated TrackerSparqlConnection. Basically store and mining handled by the client app.
-
Carlos Garnacho authored
It must listen to the signal from the right tracker-store instance.
-
Carlos Garnacho authored
This allows tracker-miner-rss to dump data on other domain ontologies than the default one.
-
Carlos Garnacho authored
This allows tracker-extract to dump data on other domain ontologies than the default one.
-
Carlos Garnacho authored
This allows tracker-miner-apps to dump data on other domain ontologies than the default one.
-
Carlos Garnacho authored
This allows running tracker-miner-fs on other domain ontologies moderated by a tracker-store daemon. The switch does: 1) Set up the ontology domain for the default TrackerSparqlConnection 2) Make the miner use a DBus name relative to the domain In result, tracker-miner-fs can take a different DBus name and talk to other tracker-store instances than the default.
-
Carlos Garnacho authored
Add a global tracker_sparql_connection_set_domain() call that allows setting domain ontology that the client shall use. This only affects the connection obtained through tracker_sparql_connection_get(), other constructors may have different settings.
-
Carlos Garnacho authored
So we can include libtracker-common vapi without conflicts
-
Carlos Garnacho authored
-
Carlos Garnacho authored
This makes Tracker behave as it ever used to. Also add some comments so it serves as a base for other domain ontologies.
-
Carlos Garnacho authored
This just wraps the information that can be extracted from a domain ontology rule file.
-
Carlos Garnacho authored
i.e. just remove the ontology name from there. We do add the ".Tracker1" suffix though, just so Tracker gets its own namespace dependent on it, eg: org.gnome.Photos.Tracker1 org.gnome.Photos.Tracker1.Miner.Files org.gnome.Photos.Tracker1.Miner.Extract
-
Carlos Garnacho authored
Only allow --domain-ontology/-d to specify the rule name. There is too much room for failure making it possible to provide all switches manually (eg. missing ones, or pointing to the wrong location). The ontology rules are installed at /usr/share, so presumably the author(s) know what they are doing.
-
Carlos Garnacho authored
-
Carlos Garnacho authored
Let's make the DBus name customizable, but making the DBus paths customizable too seems a bit overkill. It is fine to have multiple services implementing /org/freedesktop/Tracker1/* objects
-
Carlos Garnacho authored
And shift all miner dbus handling from TrackerMiner. This object takes a TrackerMiner and implements the org.freedesktop.Tracker1.Miner interface for it on DBus. One notable difference in handling here is that libtracker-miner does not try to own DBus names anymore, that is left up to the caller. The registered object will be available on whatever dbus name the caller does register. For compatibility, all TrackerMiner implementations around have been made to request their usual name.
-
Carlos Garnacho authored
The signal marshaller has an extra argument, that was not available in the class method.
-