1. 03 Jul, 2018 2 commits
  2. 24 Jun, 2018 1 commit
    • Sam Thursfield's avatar
      Run tests using `meson test`, rather than running `py.test` directly · 15dc5aa4
      Sam Thursfield authored
      In order to instantiate the Application class and test the toplevel
      logic we need to be able to load the resource files. We can either
      add custom hacks to py.test to find them in the /app director, or
      use Meson as a wrapper that tells py.test where to find the files.
      
      I have picked the Meson-as-a-wrapper approach since it will hopefully
      be more robust.
      15dc5aa4
  3. 17 Jun, 2018 2 commits
  4. 03 Jun, 2018 1 commit
    • Sam Thursfield's avatar
      Remove ref for tagcloud.bst · c43e26d4
      Sam Thursfield authored
      This references the repository that contains the file, it causes
      an infinite loop if we try to store the ref of the commit containing
      that file in the commit whose ref we need to store ...
      c43e26d4
  5. 02 Jun, 2018 1 commit
  6. 28 Apr, 2018 1 commit
    • Sam Thursfield's avatar
      Need to set GIO_EXTRA_MODULES when running from a prefix · 2240ee6b
      Sam Thursfield authored
      Otherwise the DConf GIO module is not loaded by subprocesses that
      we launch, which prevents them interacting with DConf.
      
      We currently launch `gsettings` as a subprocess from trackerappdomain
      as a workaround for the issue that the GSettings API doesn't let us
      manage multiple DConf profiles within a single process.
      2240ee6b
  7. 22 Apr, 2018 1 commit
    • Sam Thursfield's avatar
      Use trackerappdomain instead of our own thing · e75b9844
      Sam Thursfield authored
      This also fixes an issue where we weren't actually using the Tracker
      libraries from the install prefix. It seems to be impossible to make
      these be picked up automatically as if we call
      GIRepository.prepend_library_path() then all hell breaks loose.
      Instead I updated the README with the correct magic env vars to use.
      
      Everyone except developers will likely run Tagcloud via Flatpak in any
      case as it is already a lot of work to build all the dependencies by
      hand.
      e75b9844
  8. 18 Oct, 2017 1 commit
    • Sam Thursfield's avatar
      Initial support for running in a separate Tracker domain · 91be94ba
      Sam Thursfield authored
      See README for context. We'll continue to default to using session-wide
      Tracker services, but this option allows testing out new version of
      Tracker without having to install stuff into /usr, and will also allow
      running in a more restricted Flatpak sandbox.
      91be94ba
  9. 03 Oct, 2017 1 commit
  10. 29 Sep, 2017 1 commit
  11. 28 Sep, 2017 1 commit
  12. 27 Sep, 2017 1 commit
  13. 25 Sep, 2017 1 commit
  14. 18 Aug, 2017 2 commits
  15. 09 Aug, 2017 1 commit
  16. 08 Aug, 2017 1 commit