distribution: admit the blueline kernel packages
This commit is contained in:
parent
1fce9d1d54
commit
4934f80e30
4 changed files with 16 additions and 14 deletions
|
|
@ -1,16 +1,10 @@
|
|||
# TASK 25 — One gitea repo for every SouveraineOS package
|
||||
|
||||
**Status:** 2026-07-30 — **Pixel3Arch now publishes every device package.**
|
||||
`packages.yml` builds + signs all of them into the additive `edge` release,
|
||||
so `pacman -Sl souveraine-aarch64` is the complete live manifest: 14 packages
|
||||
(souveraine, -callaudio, -q6voiced, -ucm-blueline, -updater, upower-souveraine,
|
||||
pulse-native-provider, souveraine-osk-switch, hexagonrpc-blueline,
|
||||
tqftpserv-blueline, blueline-edge-sense, souveraine-stevia,
|
||||
souveraine-squeekboard, usb-signaller). Two deferred on purpose: `hyprgrass`
|
||||
(Hyprland plugin, phased out for viewtop) and `libssc-souveraine` (phone runs
|
||||
upstream libssc; our fork isn't deployed). **Goal achieved:** push → `pacman
|
||||
-Syu` on the phone, no hand-carried packages. The kernel (`kernel.yml`) is the
|
||||
last holdout — it still ships a raw `.pkg.tar.zst` with no `repo-add --sign`.
|
||||
**Status:** 2026-08-13 — Pixel3Arch now has one package workflow. Its device
|
||||
and kernel jobs publish signed artifacts into the additive `edge` release and
|
||||
validate every emitted artifact against the central distribution contract. The
|
||||
former raw `kernel-latest` release path is retired; its first shared-archive CI
|
||||
proof remains required before calling the kernel delivery complete.
|
||||
|
||||
## The problem in one line
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue