2026-09-26 –, 5053.1 (Großer B-IT Raum)
The current architecture for building Alpine and postmarketOS packages has served us well. But it's time to reevaluate our requirements and design a new system.
Today, we still rely on Lua scripts written over ten years ago to build all of our repositories. But Alpine has grown a lot since then: we have many new architectures (one of which, riscv64, is unbelievably slow...), and a single failing test in one package still blocks the upload of all other, unrelated packages. TL;DR: the builders are very often the bottleneck of Alpine development.
To meet our needs today, I'll propose some requirements I think a new architecture should have, along with an idea for what it could look like. Hopefully we can find some interested people and build the "Next Gen. Alpine-Builder"™.
Computer science student at RWTH Aachen and a developer for both Alpine Linux and postmarketOS. Maintainer of various Alpine packages including LLVM, the GNOME stack and the stable Linux kernel. Also responsible for GNOME/Phosh UI integration in postmarketOS and the coordination between Alpine and pmOS. https://achill.org/
Long-time Alpine developer, first-time presenter.
Hi! I'm Patrycja [/paˈtrɘ.t͡sja/], DevOps engineer by day, FOSS enthusiast by night. I maintain ~400 packages in Alpine – notably, most of Mozware – as well as review MRs and handle silly issues. I've also been rather fascinated by making things work on Alpine/musl, like Spotify, Firefox, or Servo[1][2], trying to upstream fixes whenever possible.
Besides that, I'm really keen on useful tooling[3][4][5] – if you're like me in that regard, stay tuned for my talk <3