Clarify Hyprland backport updates and rebuild scheduling

This commit is contained in:
Scott Jones committed 2026-09-26 23:44:18 -04:00
1 parent 88629b46b5
commit f6f0da2a98
1 file changed
+3 -1
+3 -1
View File
@@ -1,5 +1,7 @@
# Hyprland software-rendering backport
Upstream version bumps are held (`sync: false`) while v0.56.2 carries [Hyprland #16343](https://github.com/hyprwm/Hyprland/pull/16343) as `software-renderer.patch`. `prepare()` applies that patch with `--fuzz=0`. Hyprland's `release_ring: fast` builds edge, rc, and stable from this recipe, so the version stays pinned until the backport is removed on purpose. Aquamarine changes still rebuild the package through `rebuild_on`.
Automatic upstream version bumps are held (`sync: false`) while the packaged release carries [Hyprland #16343](https://github.com/hyprwm/Hyprland/pull/16343) as `software-renderer.patch`. `prepare()` applies that patch with `--fuzz=0`. Hyprland's `release_ring: fast` builds edge, rc, and stable from this recipe. Aquamarine changes in the official/ALARM repositories are checked by the separate six-hour `sync-rebuilds` job through `rebuild_on`, which proposes a package release bump for rebuilding.
The hold does not require staying on v0.56.2 until #16343 lands. If a newer upstream release does not yet include the fix, update `pkgver`, rebase the patch and refresh its checksum, and test software rendering and accelerated rendering before publishing. Keep `sync: false` while the backport is needed.
Remove `sync: false` and `software-renderer.patch` in the same change once the selected upstream release includes the #16343 behavior. Set `pkgver` to that release, then test software rendering and accelerated rendering before publishing.