| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Fixes regression in commit b458fda8fa03f5ec53f8de9edfeef1b7610aae9c.
See https://developer.gnome.org/hig/stable/typography.html
|
|
|
|
|
| |
This also adds `tracker extract -o json` to dump resources in JSON-LD,
in anticipation of corresponding updates in tracker-miners.git.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=794496
|
|
|
|
| |
This was causing the command to fail.
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes:
GLib-GObject-CRITICAL **: g_object_unref: assertion
'G_IS_OBJECT (object)' failed
when calling "tracker daemon"
https://bugzilla.gnome.org/show_bug.cgi?id=788883
|
|
|
|
|
|
|
| |
Every command switch should return properly. Otherwise the code
reaches g_warn_if_reached () and a warning is printed.
https://bugzilla.gnome.org/show_bug.cgi?id=788680
|
|
|
|
|
|
|
| |
The Since tag was bumped because the method's signature has changed.
It is not backwards compatible with the one that was added in 0.10.
https://bugzilla.gnome.org/show_bug.cgi?id=787246
|
|
|
|
|
|
| |
Make "tracker status --stat" offer info for all RDF classes right away,
instead of trying to figure out the "common" ones from the formats handled
by tracker extract modules/rules, which are not in this repo anymore.
|
|
|
|
|
|
|
| |
There can now be multiple instances looking into separate database
and journal locations. TrackerDataManager has been made an initable
too, and busy handling has been lifted to a signal, in order to
reduce the arguments at new() a bit.
|
|
|
|
|
|
| |
It's turned into a singleton pointer in tracker-data-manager.c atm,
but now multiple DB managers pointing to different locations are
possible.
|
|
|
|
|
|
|
|
| |
We keep two separate writers, one for the ontology and another one
for regular data. The ontology one is just used during database
initialization and is not expected to survive past
tracker_data_manager_init(). The second writer will remain in place
in order to dump user updates.
|
|
|
|
|
|
|
|
| |
And call it directly from the "tracker reset" subcommand, which seems
about the only place where this is needed.
In the future, we should just consider cache/journal directory ours,
delete those altogether, and avoid these horrible layering breaks.
|
|
|
|
|
| |
We already pass a GFile with the location, just use the predefined basename
for these.
|
|
|
|
|
| |
This is necessary to make the journals ubiquitous, as otherwise we mangle
the canonical database when opening other ones.
|
| |
|
|
|
|
|
|
| |
cache/journal/ontology dirs are now mandatory in
tracker_data_manager_init(), all the upper layers must know what
database and ontology they are using.
|
|
|
|
| |
This is superfluous now that we can load ontologies from custom places.
|
|
|
|
|
|
|
|
|
|
|
|
| |
/opt/tracker/share# cat tracker/domain-ontologies/test.rule
[DomainOntology]
DataLocation=%HOME%/.cache/test/data
CacheLocation=%HOME%/.cache/test/cache
OntologyLocation=%SHAREDIR%/tracker/ontologies
Domain=test
DBusPath=/test
OntologyName=test
|
| |
|
| |
|
|
|
|
| |
specific ontologies
|
|
|
|
|
|
|
|
|
|
| |
First, instead of using add_global_arguments() we now use a variable
to set global compiler args. It turns out that add_global_arguments()
is broken if you ever want to include your project as a subproject of
something else.
Second, dependencies weren't being specified correctly. These are
hopefully now fixed to avoid any more random build failures.
|
|
|
|
| |
Hopefully among the last ones!
|
|
|
|
|
|
|
| |
This is useful for people who are not building from Git but still want
to avoid Autotools.
See: https://mail.gnome.org/archives/desktop-devel-list/2017-April/msg00091.html
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
See <http://mesonbuild.com/> for information about Meson.
Remaining issues:
* There's no `make dist` equivalent. We currently produce release
tarballs containing the output files of the Vala compiler. We need
to think through whether we can stop doing that. Shipping the
generated .c files does make the Vala preprocessor useless so
it would be good if we can stop.
* The Firefox, Thunderbird, Evolution and Nautilus plugins are not
built
* https://github.com/mesonbuild/meson/issues/671 -- means we can't
depend on tracker_common_dep in most places and have to manually
set link_with, include_directories and sources instead.
* https://github.com/mesonbuild/meson/issues/1469 -- without this we
have to install generated Vala headers using a script
* https://github.com/mesonbuild/meson/issues/1229 -- means adding
the #include guard to libtracker-sparql/tracker-generated-no-checks.h
is a pain
* The test suite has some spurious failures.
Here's a rough speed comparison.
Meson:
time sh -c 'meson .. --prefix=/opt/tracker-meson -D bash_completion=/opt/tracker-meson/share/bash-completion -Dsystemd_user_services=/opt/tracker-meson/lib/systemd/user -Ddbus_services=/opt/tracker-meson/share/dbus-1/services && ninja-build -j 4 && ninja-build install'
real 1m8.194s
user 2m16.962s
sys 0m20.532s
Autotools:
time sh -c './configure --prefix=/opt/tracker-autotools --with-bash-completion-dir=/opt/tracker-autotools/share/bash-completion --with-session-bus-services-dir=/opt/tracker-autotools/share/dbus-1/services --disable-nautilus-extension && make -j 4 && make install'
real 2m37.750s
user 4m37.214s
sys 0m54.806s
Plus 30+ seconds of ./autogen.sh first.
Note that Meson builds may fail if your source tree has generated files
from an Autotools build in there. If you see errors about duplicate
definitions, first try cleaning your source tree (use `git clean -dfx`,
but make sure you commit any work first!!)
|
|
|
|
|
|
| |
It's a bit ugly that GLib string functions take signed chars and
SQLite'3 string functions return unsigned chars. We could disable
that warning instead but maybe it's useful in some other places.
|
| |
|
|
|
|
| |
They need to be exactly one line above a string to show up in .po files.
|
|
|
|
|
|
| |
And make it clear we poke the GError contents if there is one,
although next() isn't really expected to fail on a "SELECT
COUNT..." query.
|
|
|
|
|
|
|
| |
The -r/--remote switch can be used to specify the base url to be used
in queries.
https://bugzilla.gnome.org/show_bug.cgi?id=773031
|
|
|
|
| |
It was doing nothing, missing the actual execution of the query.
|
|
|
|
|
| |
And use GSettingsSchema/GSettingsSchemaSource. This code is still
disgusting.
|
|
|
|
| |
See https://developer.gnome.org/hig/stable/typography.html
|
|
|
|
|
|
|
|
|
|
| |
We used to poke a third column when the "no search term given" queries just
return 2. This triggers warnings in the bus backend, but doesn't with the
direct backend, which just returns NULL.
Some people are seeing these warnings, which sounds bad enough because it
means tracker is forcing the "bus" backend for some reason. But of all ways
to notice this situation, this should not be one.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
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...
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This wraps `$libexecdir/tracker-extract --file`. I think that the
extractor is a really important part of Tracker that needs to be
accessible in a standard way.
Currently the output of `tracker-extract --file` contains a lot of
log information even with `--verbosity=0`. And dumping the result as
a SPARQL UPDATE operation isn't ideal, it'd be nicer to output Turtle
or something.
https://bugzilla.gnome.org/show_bug.cgi?id=751991
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If you run `tracker index` with no arguments you get the help output.
However, if you ran `tracker index ~/myfile` before you would see this:
(tracker index:28627): Tracker-WARNING **: (tracker-index.c:369):index_run: code should not be reached
Now you get a more helpful message:
Use `tracker index --file` when giving a specific file or directory
to index. See `tracker help index` for more information.
We could probably just assume --file if no mode is passed, but let's do
that separately. To be honest, `tracker index` should probably only take
a file or a mimetype, and the --backup, --restore and --import modes
should become commands in their own right.
|
|
|
|
|
|
| |
Must be unref'ed after the loop. Fixes crash if >1 files are provided.
https://bugzilla.gnome.org/show_bug.cgi?id=767024
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
This is possibly a data loss situation, so warn the user that this is
possibly what will happen.
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=761177
|
| |
|
|
|
|
| |
This was scheduled for removal for 1.6, a bit late here.
|
|
|
|
|
|
|
|
|
| |
Owner UID of the /proc/[pid]/cmdline could be different than process real UID
while /proc/[pid] owner is expected to be equal.
Signed-off-by: Denis Zalevskiy <denis.zalevskiy@jolla.com>
https://bugzilla.gnome.org/show_bug.cgi?id=755945
|
|
|
|
|
|
|
|
|
| |
- Support JHBuild too
- Allow disabling altogether
- Fix DISTCHECK flags
Conflicts:
Makefile.am
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=752871
|
|
|
|
|
| |
We now autocomplete files where it applies (various -f/--file options,
tracker info) and '-' prefixed switches.
|
|
|
|
| |
The help strings in the sql subcommand weren't marked as translated
|