| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
|
|
|
| |
There is a --enable/disable-png check below.
|
|
|
|
|
|
|
| |
So I can use G_DECLARE_DERIVABLE_TYPE() instead of writing out
everything manually.
https://bugzilla.gnome.org/show_bug.cgi?id=767472
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
sqlite3_errstr was added in that version.
https://bugzilla.gnome.org/show_bug.cgi?id=743245
|
|
|
|
| |
We can point to the tracker product.
|
|
|
|
|
|
|
|
|
|
| |
Only do this if we need to load the FTS5 module, sqlite3 might have
been compiled with SQLITE_OMIT_LOAD_EXTENSION, which will make things
go very wrong (poking NULL vfuncs in a 0'ed out sqlite3_api_routines)
at runtime.
This facility must be enabled if we need to load our FTS module, so
bail out at configure time if it's not there.
|
|
|
|
|
| |
It seems to break the build because of an Automake bug, see:
<http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13928>
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 5ae20fb915659163e68f5f18bbd444e8de30d02b.
Lesson learned (again): don't do something just because Automake tells
you to.
Notice the same thing happened back in commit e46bfc1c43 which
was reverted again in b1e3997ce7b894.
|
|
|
|
|
|
| |
Based on this warning from libtoolize:
libtoolize: `AC_PROG_RANLIB' is rendered obsolete by `LT_INIT'
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes the following warnings:
src/libtracker-miner/Makefile-shared-sources.decl:5: warning: source file '$(top_srcdir)/src/libtracker-miner/tracker-monitor.c' is in a subdirectory,
src/libtracker-miner/Makefile-shared-sources.decl:5: but option 'subdir-objects' is disabled
src/libtracker-miner/Makefile.am:10: 'src/libtracker-miner/Makefile-shared-sources.decl' included from here
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'
automake: automake option hasn't been enabled. For now, the corresponding output
automake: object file(s) will be placed in the top-level directory. However,
automake: this behaviour will change in future Automake versions: they will
automake: unconditionally cause object files to be placed in the same subdirectory
automake: of the corresponding sources.
automake: You are advised to start using 'subdir-objects' option throughout your
automake: project, to avoid future incompatibilities.
src/tracker-preferences/Makefile.am:34: warning: source file '$(top_srcdir)/src/miners/fs/tracker-config.c' is in a subdirectory,
src/tracker-preferences/Makefile.am:34: but option 'subdir-objects' is disabled
src/libtracker-miner/Makefile-shared-sources.decl:17: warning: source file '$(top_srcdir)/src/libtracker-miner/tracker-crawler.c' is in a subdirectory,
src/libtracker-miner/Makefile-shared-sources.decl:17: but option 'subdir-objects' is disabled
tests/libtracker-miner/Makefile.am:11: 'src/libtracker-miner/Makefile-shared-sources.decl' included from here
src/libtracker-miner/Makefile-shared-sources.decl:5: warning: source file '$(top_srcdir)/src/libtracker-miner/tracker-monitor.c' is in a subdirectory,
src/libtracker-miner/Makefile-shared-sources.decl:5: but option 'subdir-objects' is disabled
tests/libtracker-miner/Makefile.am:11: 'src/libtracker-miner/Makefile-shared-sources.decl' included from here
autoreconf: automake failed with exit status: 1
|
| |
|
|
|
|
|
|
|
| |
Allow optional support for the libcue 2.0.0 API changes: new location of
libcue.h and a renamed enum.
https://bugzilla.gnome.org/show_bug.cgi?id=762512
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Our old stale copy of the FTS3/4 module is now deleted, replaced by
a shinier FTS5 embedded module. If at configure time we detect that
SQLite doesn't offer the FTS5 module, we will load our own, just as
we used to do with FTS4.
FTS5 brings a few differences in the ways it's meant to be extended,
the tokenizer has been updated to cope with the differences. Also,
FTS5 offers no offsets() builtin function, nor matchinfo() which we
used to implement ranking. It offers though ways to implement
additional functions, and builtin rank support which can be tweaked
to achieve the same functional results than we did.
Other than that, the ways to interact with the FTS virtual table
are roughly similar to those in FTS4, insertions and deletions have
been updated to do things the FTS5 way.
Since it's not worth to bump the database format (data is reproducted
from the journal, so we drop some embedded data such as
nie:plainTextContent), the nco:hobby property has been modified to
no longer be fulltext indexed, AFAIK there's no users ever setting/
accessing that, and the FTS properties change will trigger the
regeneration of the FTS view and virtual tables, resulting in a
seamless update to FTS5.
However, we don't leave completely unscathed from the fts3_tokenizer()
change. Since the older FTS3/4 tokenizer is not registered, we can't
just drop the older FTS table. So it is left dangling and never
accessed again, in favor of the newer fts5 table. This is obviously
not a problem when creating the database from scratch.
In the way, a few bugs were found. per-property weights in ranking
were being given in a scrambled way (although stable across database
generations). And deletion of FTS properties (or entire rows) could
result in the tokens not being fully removed from the FTS table,
resulting in confused searches. These are now fixed.
Impact to users of tracker should be none. All the FTS Sparql-to-SQL
translation has been updated to just use FTS5 syntax and tables.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
When "Couldn't" is used in an m4 macro, vim will highlight all the
code until the next "'" to close it. Work around that by replacing
"Couldn't" by "Could not".
https://bugzilla.gnome.org/show_bug.cgi?id=755218
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
- Support JHBuild too
- Allow disabling altogether
- Fix DISTCHECK flags
Conflicts:
Makefile.am
|
| |
|
|
|
|
|
|
| |
and now grss has unversioned pc name
Signed-off-by: Igor Gnatenko <ignatenko@src.gnome.org>
|
|
|
|
|
|
|
| |
There are no API break since 0.5, but 0.5 doesn't work well and doesn't shipped in distros
Reference: https://bugzilla.gnome.org/show_bug.cgi?id=752371
Signed-off-by: Igor Gnatenko <ignatenko@src.gnome.org>
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=750368
|
|
|
|
|
|
|
| |
There's places where CFLAGS is modified/restored while LDFLAGS is left
untouched, both should be saved/restored at the same time.
https://bugzilla.gnome.org/show_bug.cgi?id=742186
|
|
|
|
|
| |
This is now unused, so remove the tool, and the configure.ac check
for fdp.
|
|
|
|
| |
Signed-off-by: Ralph Boehme <slow@samba.org>
|
|
|
|
|
|
| |
Rename the bash completion script after the binary and move it to
/usr/share/bash-completion/completions. This way the completions can be
loaded on demand.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=743250
|
| |
|
| |
|
| |
|
| |
|