1. 02 Jul, 2018 3 commits
  2. 01 Jul, 2018 4 commits
  3. 06 Feb, 2018 1 commit
  4. 16 Dec, 2017 1 commit
    • Sam Thursfield's avatar
      Rename libtracker-common to libtracker-miners-common · 3cee7b92
      Sam Thursfield authored
      We made a big compromise when splitting tracker core from tracker-miners
      in that the common code that was needed by both parts would end up
      duplicated. It's ugly but it works fine at the moment and allows us to
      keep all of the common code private.
      
      I had an issue when trying to embed tracker core into tracker-miners as
      a Meson subproject though. Having two targets named tracker-common
      caused confusion as duplicate targets aren't allowed, but they are not
      quite equivalent so we can't just pick one or the other.
      
      To work around this, I've renamed the copy in this repo to
      tracker-miners-common. This only affects the target names, not the
      actual function names.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=789725
      3cee7b92
  5. 01 Dec, 2017 2 commits
  6. 02 Nov, 2017 1 commit
  7. 29 Sep, 2017 1 commit
  8. 12 Aug, 2017 1 commit
  9. 03 Aug, 2017 1 commit
    • Carlos Garnacho's avatar
      Remove code not related to miners · 63af0cfe
      Carlos Garnacho authored
      The miners are being split from the core tracker package.
      
      On both autotools/meson builds, datadir and libdir for
      private data has been changed to be separate from the tracker
      core. Same goes for the gettext package and other bits.
      
      Additionally, avoid installing the dbus xml descriptions.
      That's fairly non-standard and unnecessary with introspection.
      63af0cfe
  10. 19 Jul, 2017 1 commit
  11. 10 Jul, 2017 1 commit
    • Carlos Garnacho's avatar
      tests: Adapt tracker-backup-test to non-GPrivate interfaces · 3cc3de69
      Carlos Garnacho authored
      This code relies on being able to query again the contents immediately
      after restore, this may or may not be true depending on the
      TrackerDBInterface used on the posterior query (eg. not being the one
      that performed the update).
      
      Since testing access from multiple DBInterfaces is not in the scope
      of this test, just add an extra TrackerDataManager initialization in
      between to ensure the interface used on the query is up to date.
      3cc3de69
  12. 09 Jul, 2017 1 commit
    • Carlos Garnacho's avatar
      libtracker-miner: Remove Tracker[File]Enumerator · 7365fd11
      Carlos Garnacho authored
      This is a pretty pointless shallow wrapper to GFileEnumerator. Just make
      TrackerDataProvider offer GFileEnumerators. If anyone ever was in need for
      implementing a TrackerEnumerator, they can do the very same by implementing
      GFileEnumerator, and handing those from their TrackerDataProvider impl.
      
      This also cuts a level of indirection in directory crawling (i.e. no
      wrapping of GTasks in GTasks), and allows us to fully use GFileEnumerator
      API (eg. g_file_enumerator_next_files will be handy).
      7365fd11
  13. 02 Jul, 2017 1 commit
  14. 29 Jun, 2017 18 commits
  15. 28 Jun, 2017 3 commits