Open BeatLink opened 3 years ago
I could see this as useful to testers. But as we don't have intermediary versions between each release, I wouldn't know at which time we should release a nightly build. This goes the same for binary nightly builds. @diegogangl, @nekohayo
Hi, sorry for being MIA :p We have a flatpak manifesto for nightly or dev versions. The actual flatpak could be generated automatically with some build system, so the only thing to do really would be set that up and add a link. I've seen this in some projects in Gnome's Gitlab (Pitivi I think?). Not sure if it can be done through Github
What about github actions?
I believe that the flatpak outputted by https://github.com/getting-things-gnome/gtg/actions/workflows/weekly_flatpak.yml doesn't work. I downloaded the one from https://github.com/getting-things-gnome/gtg/actions/runs/9311435996#artifacts and got:
$ flatpak install org.gnome.GTG.Devel_20240530.flatpak
error: The application org.gnome.GTG.Devel/x86_64/master requires the runtime org.gnome.Platform/x86_64/master which was not found
Looking at
$ flatpak install org.gnome.Platform
Looking for matches…
Similar refs found for ‘org.gnome.Platform’ in remote ‘flathub’ (system):
1) runtime/org.gnome.Platform/x86_64/3.24
2) runtime/org.gnome.Platform/x86_64/3.26
3) runtime/org.gnome.Platform/x86_64/3.28
4) runtime/org.gnome.Platform/x86_64/3.30
5) runtime/org.gnome.Platform/x86_64/3.32
6) runtime/org.gnome.Platform/x86_64/3.34
7) runtime/org.gnome.Platform/x86_64/3.36
8) runtime/org.gnome.Platform/x86_64/3.38
9) runtime/org.gnome.Platform/x86_64/40
10) runtime/org.gnome.Platform/x86_64/41
11) runtime/org.gnome.Platform/x86_64/42
12) runtime/org.gnome.Platform/x86_64/43
13) runtime/org.gnome.Platform/x86_64/45
14) runtime/org.gnome.Platform/x86_64/44
15) runtime/org.gnome.Platform/x86_64/46
Which do you want to use (0 to abort)? [0-15]:
it seems that https://github.com/getting-things-gnome/gtg/blob/c501ff800e4517f66b3254f373d41bf9afd861fa/build-aux/org.gnome.GTG.Devel.json#L4 doesn't work and we should use something like "runtime-version": "46"
instead, and keep it up to date.
When I have a minute, I'll be working on:
This will allow me to keep up with the bleeding edge of GTG on my Debian work laptop :)
flatpak install
and flatpak run
.Now I'd like to upload the artifacts "somewhere", to enable getting the latest weekly via a simple flatpak update
. I'm not super sure about the "somewhere". GTG stable is uploaded to Flathub, and Flathub has a beta channel. But I'm not sure that it's reasonable to brand a weekly build as "beta". I see that Fractal publishes their "Development version" to https://nightly.gnome.org/, but that seems to be for GNOME apps.
I thought about trying to create my own flatpak repo but A- that's an entire rabbit hole and B- it's not great to tie a GTG feature to a single person (even though it looks like I'm the only one trying to use the weekly flatpak). Or it might be possible to just host it using GitHub pages.
OK, starting from the run on July 5th, the weekly flatpak works :)
It still thinks it's running 0.6 though: I'll see if I can get it to say something like 0.7.0-dev-20240705.
It would be great if GTG could have nightly flatpak builds from the master branch. This would make the bleeding edge features available to user, which would mean more users willing to beta test