1. 23 Feb, 2017 1 commit
  2. 19 Jan, 2017 1 commit
  3. 16 Dec, 2016 1 commit
  4. 08 Dec, 2016 2 commits
  5. 14 Oct, 2016 1 commit
  6. 19 Sep, 2016 1 commit
  7. 14 Sep, 2016 1 commit
  8. 23 Aug, 2016 2 commits
  9. 10 Aug, 2016 1 commit
  10. 14 Jul, 2016 1 commit
  11. 21 Jun, 2016 1 commit
  12. 13 Jun, 2016 1 commit
  13. 30 May, 2016 1 commit
  14. 14 May, 2016 1 commit
  15. 08 May, 2016 2 commits
  16. 27 Mar, 2016 5 commits
    • Carlos Garnacho's avatar
      configure: Check that sqlite3 has sqlite3_auto_extension() enabled · f3db8b28
      Carlos Garnacho authored
      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.
    • Sam Thursfield's avatar
      configure.ac: Add note about Automake subdir-objects option · 7e72eb23
      Sam Thursfield authored
      It seems to break the build because of an Automake bug, see:
    • Sam Thursfield's avatar
      Revert "configure: Use subdir-objects Automake option" · 148922eb
      Sam Thursfield authored
      This reverts commit 5ae20fb9.
      Lesson learned (again): don't do something just because Automake tells
      you to.
      Notice the same thing happened back in commit e46bfc1c which
      was reverted again in b1e3997c.
    • Sam Thursfield's avatar
      configure: Remove AC_PROG_RANLIB, it's not needed · 826c8702
      Sam Thursfield authored
      Based on this warning from libtoolize:
          libtoolize: `AC_PROG_RANLIB' is rendered obsolete by `LT_INIT'
    • Sam Thursfield's avatar
      configure: Use subdir-objects Automake option · 5ae20fb9
      Sam Thursfield authored
      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
  17. 21 Mar, 2016 2 commits
  18. 14 Mar, 2016 2 commits
  19. 01 Mar, 2016 2 commits
    • Carlos Garnacho's avatar
      Release 1.7.4 · 6ef58346
      Carlos Garnacho authored
    • Carlos Garnacho's avatar
      Update to FTS5 · e6bd45c2
      Carlos Garnacho authored
      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.
  20. 15 Feb, 2016 1 commit
  21. 17 Jan, 2016 1 commit
  22. 17 Dec, 2015 1 commit
  23. 25 Nov, 2015 1 commit
  24. 25 Sep, 2015 1 commit
  25. 22 Sep, 2015 1 commit
  26. 19 Aug, 2015 1 commit
  27. 31 Jul, 2015 1 commit
  28. 21 Jul, 2015 1 commit
  29. 18 Jul, 2015 1 commit
  30. 14 Jul, 2015 1 commit