1. 27 May, 2018 1 commit
  2. 16 May, 2018 1 commit
  3. 11 May, 2018 1 commit
  4. 05 May, 2018 1 commit
    • Jehan's avatar
      build: update nightly and dev flatpak. · 1ef0f506
      Jehan authored
      In particular a bunch of dependencies were moved to the BaseApp.
      Dev flatpak is actually a bit useless now (since last dev release is
      older than stable). But I keep the dev manifest around to make it easier
      to update for the future when we'll have a new dev release.
  5. 06 Apr, 2018 2 commits
  6. 19 Mar, 2018 1 commit
  7. 14 Jan, 2018 1 commit
    • Jehan's avatar
      Rename gimp.appdata.xml.in to org.gimp.GIMP.appdata.xml.in.in. · 458e3130
      Jehan authored
      I completely forgot to rename the appstream file according to the new
      ID. While doing so, I also make it a .in.in file, with initial
      processing by the autotools. Indeed I need @GIMP_COMMAND@ to be replaced
      by AC_CONFIG_FILES().
      Finally I fix a badly closed XML tag (which reminds me I should always
      test a commit, even when it's a simple non-C 1-liner change!).
  8. 05 Jan, 2018 1 commit
  9. 04 Jan, 2018 1 commit
  10. 02 Jan, 2018 1 commit
  11. 07 Oct, 2017 2 commits
  12. 06 Oct, 2017 1 commit
  13. 05 Oct, 2017 2 commits
    • Jehan's avatar
    • Jehan's avatar
      build: base both the dev and nightly builds off a BaseApp. · 54f4f445
      Jehan authored
      Keeping all dependencies inside the main manifest is very annoying
      because flatpak-builder will check them every time the package is
      rebuilt. Worse, sometimes the cache won't be hit (even though it should
      have), resulting into a rebuild of many dependencies. I create a BaseApp
      build which is the recommended process (and not creating our own runtime
      based on GNOME one's, as I first thought) which won't need to be built
      as often as the main manifests. The other advantage is obviously that
      this BaseApp can be shared between the dev and nightly (and likely even
      the stable later) builds. I will only keep differences inside the main
      manifests (for instance lcms2 which requires a higher version on master
      than on the GNOME runtime and the last dev release).
      I also move webkitgtk as the first dependencies since it takes too long
      and flatpak uses a sequential dependency graph (so any change to a
      previously listed dependency, even when actually unrelated, was
      triggering a rebuild of webkitgtk!).
      Only remaining issue is that I don't manage yet to run the cleanup of
      the BaseApp at the end of the main manifests (for files needed for
      building, but not at runtime).
  14. 23 Sep, 2017 1 commit
  15. 20 Sep, 2017 2 commits
  16. 02 Jun, 2017 1 commit
  17. 01 Jun, 2017 1 commit
  18. 13 Apr, 2017 1 commit
  19. 13 Feb, 2017 2 commits
    • Jehan's avatar
      build: workaround python2 crashes in Flatpak. · c8ebd043
      Jehan authored
      See the upstream issue where python2 would crash on some platforms, yet
      not others: https://github.com/flatpak/flatpak/issues/143
      For this, I disable introspection on GEGL (which is anyway not useful
      in the Flatpak build, I believe), and wrap gdbus-codegen in a temporary
      build script for GIMP to force it to use Python 3 (I can't force
      globally the $PYTHON environment variable like on Webkit because GIMP
      needs Python 2 as dependency).
    • Jehan's avatar
      build: fix Webkit build in Flatpak package. · afc69f83
      Jehan authored
      For some reason, Webkit would not build with Python 2 on a different
      machine though it did on mine. Let's just force Python 3 usage (for
      build only, not as a runtime dependency) by setting the $PYTHON
      environment variable during this build. Anyway Python 3 is available
      from the base build so it's not a new dependency.
  20. 02 Feb, 2017 1 commit
  21. 01 Feb, 2017 1 commit
    • Jehan's avatar
      build: factorize a bit the flatpak manifest. · 4c33008f
      Jehan authored
      We can actually group modules together to mark their relationship,
      and easily deactivate them together if needed.
      I grouped all Python modules, Exiv2 under GEXiv2, ilmbase under
      openEXR, and finally libpng and lcms2 under a "duplicate-dependencies"
      module to indicate that these modules are available in the runtime
      (under a lower version, below our requirements) so we should check
      whether to remove them, upon runtime update.
  22. 31 Jan, 2017 1 commit
  23. 30 Jan, 2017 2 commits
  24. 29 Jan, 2017 4 commits
    • Jehan's avatar
      build: adding network and dbus unlimited access. · 7ffba031
      Jehan authored
      This is necessary for opening files from the network.
      It is actually possible to allow only some named service bus which
      would be much more in line with proper sandboxing. But I can't find
      exactly what is the service name used for gvfs (which is the virtual
      filesystem apparently used internally for remote file access in GIO).
      Also I'm pretty sure we must use other buses for various services. We
      should make a list of what service bus are necessary for normal usage.
      For the time being though, let's just have a flatpak build with as many
      features as possible.
    • Jehan's avatar
      build: update jasper in flatpak build to version 2.0.10. · efce5d0f
      Jehan authored
      I had to figure out a few things about making CMake builds in Flatpak
      since jasper moved from autotools in recent versions.
    • Jehan's avatar
      build: adding libwmf dependency to flatpak. · ca832fb0
      Jehan authored
      Main missing dependencies now are libgudev, webkit and ghostscript.
    • Jehan's avatar
  25. 28 Jan, 2017 1 commit
    • Jehan's avatar
      build: add an initial flatpak-builder manifest. · 4245deb5
      Jehan authored
      Based on Alexander Larsson's original nightly GIMP flatpak. I updated
      most dependencies, changed some options, and added some dependencies
      whose versions were now too low in the runtime (libpng and lcms2).
      I also use the new "--filesystem=xdg-config/GIMP" option, made upon my
      request, which means we will want to use a recent flatpak.
      Many options are still missing but that's a start with a working
      flatpak manifest.