Commit Graph

19 Commits

Author SHA1 Message Date
Jehan 12aae56ede build: add a bit more info about using the Anitya db (for flatpak deps). 2021-10-20 13:12:39 +02:00
Ondřej Míchal 47be60dbe0 flatpak: Add x-checker-data to sources
The x-checker-data field in a flatpak manifest can be used together with
flatpak-external-data-checker[0] to help maintain the dependency list.

The utility has several backends including a generic solution for
scraping and parsing of websites. Instead of using that this uses
anitya[1] as a backend. Anitya is Fedora-hosted service tracking
releases of various projects, taking away the need to match the various
version patterns across projects in the manifest.

The change required some changes to links to existing sources due to
some reasons: availability upstream, change in upstream (url, forge, tar
compression). Affected modules are:

- graphviz
  > from: https://www2.graphviz.org/Packages/stable/portable_source/graphviz-2.44.1.tar.gz
  > to  : https://gitlab.com/graphviz/graphviz/-/archive/2.44.1/graphviz-2.44.1.tar.gz

- cairo
  > from: https://www.cairographics.org/releases/cairo-1.16.0.tar.xz
  > to  : https://gitlab.freedesktop.org/cairo/cairo/-/archive/1.16.0/cairo-1.16.0.tar.gz

- libx265
  > from: 3.4 git tag
  > to  : https://bitbucket.org/multicoreware/x265_git/downloads/x265_3.4.tar.gz

-openexr
  > from: https://github.com/openexr/openexr/releases/download/v2.3.0/openexr-2.3.0.tar.gz
  > to  : https://github.com/AcademySoftwareFoundation/openexr/releases/download/v2.3.0/openexr-2.3.0.tar.gz

- lcms2
  > from: 967e8ac9a17441efda57dc12d0bf84ed9188460c52eb8542d399ce9ab43bd4191988ed22b254ef34c6c1877bbb935952ed/lcms2-2.12.tar.gz
  > to  : https://github.com/mm2/Little-CMS/releases/download/lcms2.12/lcms2-2.12.tar.gz

Some sources do not have the x-checker-data set because they are usually
not developed anymore (last release over 10 years ago) or the next
version includes a major version bumb which is not a good candidate for
automation or the currently selected version is a git tag, which was not
clear to me.

[0] https://github.com/flathub/flatpak-external-data-checker
[1] https://release-monitoring.org/
2021-10-12 23:00:03 +00:00
Jehan dcba5f7f26 build: remove flathub's submodule and update flatpak howto.
Now our nightly manifest does not depend on the base module used in
flathub so just remove the submodule.
Also update our howto.
2018-06-06 02:37:41 +02:00
Jehan fc8d815ab8 build: update the flatpak howto. 2018-05-27 22:20:09 +02:00
Jehan 6463e80c71 build: update my howto for flatpak releases.
After a small fiasco of 5 consecutive builds, add some newly learned
ways to test the builds beforehand on flathub infrastructure, for the
next time.
2018-04-27 18:35:33 +02:00
luz.paz 147c09f19e Bug 795161 - Misc. typo fixes in source comments and doxygen
Found via `codespell`
Follow-up to  commit 7fdb963e01
2018-04-18 21:06:57 +02:00
Jehan 580782dc65 build: add the flathub stable repository as a submodule.
This will only be used for our development/nightly flatpak builds and
this submodule does not have to be pulled for normal GIMP development.
2017-12-06 22:34:45 +01:00
Jehan dd924bb33a build: stable flatpak manifest is now hosted at flathub. 2017-10-23 21:16:05 +02:00
Jehan e545116b89 build: run flatpak-builder with --ccache option for faster builds.
So I discover today that there is an option --ccache to request
flatpak-builder to compile using ccache, which is obviously a great idea
when rebuilding the same deps too often. Update the howto with the info.
2017-10-05 00:16:34 +02:00
Jehan a35d46d5a6 build: update the howto. 2017-09-23 13:37:56 +02:00
Jehan 8e329d25fb build: replace `flatpak build-export` by `flatpak-builder --export-only`
build-export is actually a low-level tool used by flatpak-builder. When
using it directly, debug and locale extensions were not extracted as
separate extensions (unless tweaking complicated command lines), ending
up with a huge GIMP flatpak with the current procedure.
Since flatpak 0.9.5, the option --export-only has been added to
`flatpak-builder` so that the build and the export can be made in 2
separate steps while using the high level procedure.
See: https://github.com/flatpak/flatpak/issues/824
2017-06-20 16:51:03 +02:00
Jehan 8b3f5e87d8 build: updates to the flatpak howto. 2017-06-07 16:53:00 +02:00
Jehan 639e69c627 build: bumping flatpak dependency to GNOME 3.24 runtime. 2017-06-01 22:34:04 +02:00
Jehan 9391a0ae6b build: make the flatpak remote-add call clearer. 2017-06-01 01:01:34 +02:00
Jehan 590924f856 build: update the flatpak-howto.
In particular, I didn't have the correct metadata because I was missing
appstream-compose. This should be a dependency of flatpak. But for the
time being, let's just have a note in our howto.
2017-05-12 21:44:41 +02:00
Jehan 6265282115 build: update flatpak-howto.txt to build both 32 and 64-bit from...
...same manifest.
2017-05-03 22:48:53 +02:00
Jehan c99800b104 build: update flatpak howto. 2017-01-31 00:17:32 +01:00
Jehan b8e7907a63 build: update the flatpak howto with information on runtime module list. 2017-01-30 16:41:51 +01:00
Jehan 0b7b120673 build: add a Flatpak howto.
That's a work-in-progress, but that's my current status.
2017-01-29 16:08:58 +01:00