1. 25 Aug, 2020 4 commits
  2. 22 May, 2020 2 commits
  3. 09 May, 2020 1 commit
    • Leesoo Ahn's avatar
      flatpak: Use stable-0.2.x branch of libgfbgraph · 63aa92ec
      Leesoo Ahn authored
      The library has changed the API version to 0.3.x for experiments.
      A lot of changes which may break the API/ABI would come.
      So, still highly recommend to use the 0.2 API version branch.
  4. 30 Mar, 2020 3 commits
    • Debarshi Ray's avatar
      flatpak: Sandbox GSettings use by dropping the dconf permissions · e352db1a
      Debarshi Ray authored
      Since GLib 2.60.x, GSettings' keyfile backend is capable enough to be
      the default backend for Flatpak applications. If a Flatpak doesn't
      have the necessary permissions to access dconf, GSettings will
      automatically switch to using the keyfile backend.
      This is good because dconf isn't suited for sandboxing. It uses a
      single database shared across all applications - they are free to read
      and write anything, and settings are left behind even after an
      application has been uninstalled. This leaves plenty of room for
      mischief and accidents. In comparison, the keyfile backend uses a
      separate isolated file for each Flatpak that's removed when the
      application is uninstalled.
    • Syed Kaleem's avatar
      flatpak: Fix the tracker and tracker-miners builds · 30d43499
      Syed Kaleem authored
      Intltool was removed from version 3.34 of the GNOME SDK, but it's
      still used by tracker-miners. Therefore it has to be bundled with the
      Tracker's master branches are now being used to develop version 3.0,
      and it's not ready for use [1]. Hence the build has to be switched to
      use the respective 2.3 branches.
      Some changes by Debarshi Ray.
      [1] https://discourse.gnome.org/t/tracker-has-branched-for-3-0-use-the-2-3-branch-if-you-want-stability/1889
    • Debarshi Ray's avatar
      flatpak: Fix the grilo-plugins build · 239ee904
      Debarshi Ray authored
      The grilo-plugins build has started to fallback to downloading grilo
      as a subproject if certain dependencies aren't met [1]. In this case,
      the grilo-pls-0.3 dependency is missing because it's disabled in the
      grilo build via the -Denable-grl-pls=false option.
      This is a problem because network access is not available in the build
      [1] grilo-plugins commit 34d3c5844864f0d0
  5. 19 Aug, 2019 4 commits
  6. 30 Jun, 2019 1 commit
  7. 31 May, 2019 1 commit
  8. 30 May, 2019 1 commit
  9. 04 Jan, 2019 2 commits
    • Debarshi Ray's avatar
      flatpak: Explicitly specify the LibRaw build options · b843015c
      Debarshi Ray authored
      Currently the build detects the presence of the necessary dependencies
      and automatically enables or disables the corresponding options. Unless
      someone is keeping a close eye on the build logs, a change in the
      manifest or the SDK might silently and unexpectedly change the build
      Ideally, the build would fail if a requested option can't be met, to
      draw attention to this unforeseen change.
      Unfortunately, the LibRaw build uses AC_MSG_WARN even for explicitly
      enabled build options. This means that a missing dependency won't fail
      the build even if the option was explicitly requested. While this is
      not ideal, at least listing the options makes it clear what the
      required outcome is. That way someone can manually check the logs from
      time to time and see if it's living up to the requirements.
      The set of build flags have been chosen to match the current reality of
      automatically selected options. Hence, there shouldn't be any
      user-visible change.
    • Debarshi Ray's avatar
      flatpak: Fix the LibRaw build · cd16fded
      Debarshi Ray authored
      The LibRaw-0.19.2 tarball got modified in-place to include a configure
      script: https://github.com/LibRaw/LibRaw/issues/197
  10. 03 Jan, 2019 1 commit
  11. 02 Jan, 2019 3 commits
  12. 22 Nov, 2018 1 commit
  13. 18 Nov, 2018 2 commits
  14. 03 Oct, 2018 3 commits
    • Debarshi Ray's avatar
      flatpak: Disable the installed tests for geocode-glib · 9fd62ae8
      Debarshi Ray authored
      None of the installed tests from the other modules (eg., gnome-photos
      itself) are part of the Flatpak bundle. It's also questionable how much
      value they would add to the Flatpak. The average non-technical user
      wouldn't know about them, but a contributor might find them useful.
    • Mathieu Bridon's avatar
      flatpak: Tell Tracker not to use a media extractor · fc41aa13
      Mathieu Bridon authored
      We already disable the extractor anyway, but Tracker still tries to
      build parts of it and that fails on a missing libcue.
      This commit disables that part as well explicitly.
    • Mathieu Bridon's avatar
      flatpak: Switch geocode-glib to Meson · 45356e74
      Mathieu Bridon authored
      ... instead of using the configure and Makefile adapter. The adapter
      inverts the Meson build's enable-gtk-doc option to default to false, so
      that needs to be handled.
  15. 27 Sep, 2018 1 commit
    • Debarshi Ray's avatar
      flatpak: Switch to Meson · d8f0be29
      Debarshi Ray authored
      The Autotools build didn't use --disable-dogtail, even though the SDK
      doesn't have Dogtail. It only worked because configure.ac doesn't
      actually check for the presence of Dogtail. The Meson build doesn't
      check for it either, but merely to imitate the Autotools build.
      It's better to spell out exactly what's going on.
  16. 26 Sep, 2018 2 commits
    • Debarshi Ray's avatar
      flatpak: Don't use a non-existent build flag · 993018a3
      Debarshi Ray authored
      There has never ever been a --disable-documentation build flag, yet,
      somehow it has been present in the Flatpak manifest since it was first
      added to the gnome-apps-nightly repository.
      GNOME Online Accounts has a --disable-documentation flag to disable
      generating the man page for goa-daemon(8), which is already covered by
      the --disable-backend flag. So, it might have been a typo while writing
      the manifest.
    • Jordan Petridis's avatar
      flatpak: Build liboauth against NSS · 886d93bf
      Jordan Petridis authored
      Currently available versions of liboauth, such as 1.0.3, don't build
      against OpenSSL 1.1.0, and that has been failing the nightly builds.
      It does work with NSS, though; and, for what it's worth, Fedora builds
      liboauth against NSS too.
  17. 14 Sep, 2018 1 commit
  18. 13 Sep, 2018 7 commits