1. 10 Apr, 2018 1 commit
  2. 12 Mar, 2018 1 commit
  3. 05 Mar, 2018 1 commit
  4. 20 Feb, 2018 1 commit
  5. 21 Dec, 2017 1 commit
  6. 21 Sep, 2017 1 commit
  7. 12 Sep, 2017 1 commit
  8. 06 Sep, 2017 1 commit
  9. 19 Aug, 2017 2 commits
  10. 05 Aug, 2017 1 commit
  11. 22 Jul, 2017 3 commits
  12. 11 Jul, 2017 1 commit
  13. 25 Mar, 2017 2 commits
  14. 20 Mar, 2017 1 commit
  15. 20 Sep, 2016 1 commit
  16. 14 Sep, 2016 1 commit
  17. 12 Sep, 2016 1 commit
  18. 19 Jul, 2016 1 commit
  19. 20 Jun, 2016 1 commit
  20. 19 Jun, 2016 2 commits
  21. 13 Apr, 2016 1 commit
    • Simon McVittie's avatar
      Make the systemd user unit conditional · 3e76c45a
      Simon McVittie authored
      I've implemented this by adding a --with[out]-systemduserunitdir
      configure option, because that seems to be what's conventional
      in projects where user units are configurable at all. If a user or
      distribution wants to disable these units, it's easier if they can
      pass --without-systemduserunitdir to everything, rather than checking
      whether it's spelled --disable-systemd-user-units in this particular
      project. Also, a binary enable/disable option wouldn't be noticeably
      less code.
      
      If the systemd user unit is disabled at configure time, the
      SystemdService line in the installed D-Bus service file is commented
      out. This addresses the corner-case situation where a user configures
      Evince --without-systemduserunitdir, but enables systemd activation
      for their session dbus-daemon (perhaps later). In that situation,
      we presumably want Evince to continue to use traditional activation,
      rather than trying to launch a nonexistent systemd unit.
      Signed-off-by: Simon McVittie's avatarSimon McVittie <simon.mcvittie@collabora.co.uk>
      Bug: https://bugzilla.gnome.org/show_bug.cgi?id=755897
      Reviewed-by: Carlos Garcia Campos
      3e76c45a
  22. 21 Mar, 2016 1 commit
  23. 16 Mar, 2016 1 commit
  24. 27 Feb, 2016 1 commit
    • Tom Schoonjans's avatar
      DjVu: support for utf8 filenames on Mac OS X · 9fe48d1f
      Tom Schoonjans authored
      Filename encoding on Mac OS X is in UTF-8, which means that DjVu
      documents must be opened with ddjvu_document_create_by_filename_utf8
      instead of ddjvu_document_create_by_filename.
      
      Implemented using a conditional preprocessor macro as this may affect
      other operating systems.
      
      Since ddjvu_document_create_by_filename_utf8 was added only in 3.5.22,
      the pkg-config check for djvulibre was changed accordingly.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=761161
      9fe48d1f
  25. 23 Feb, 2016 1 commit
  26. 02 Feb, 2016 1 commit
  27. 23 Nov, 2015 1 commit
  28. 19 Nov, 2015 1 commit
  29. 21 Sep, 2015 1 commit
  30. 16 Sep, 2015 1 commit
  31. 21 Jul, 2015 1 commit
  32. 22 Jun, 2015 1 commit
  33. 27 May, 2015 2 commits
  34. 29 Apr, 2015 1 commit