Package buildsystem
My personal Slackware packages for slackware64-current are built by a small pipeline of tools running inside one dedicated QEMU virtual machine. Nothing here is a single program: it is a repository that gets reassembled, a dependency layer that gets patched, a builder that turns SlackBuilds into packages, and a publishing step that puts them online at packages.danix.xyz. This page walks the whole flow in the order a build actually happens. The pipeline end to end. The green side path is the 15.0 stable test, run only for packages headed to SlackBuilds.org. // The VMThe buildsystem lives in a QEMU virtual machine running slackware64-current, kept up to date with slackpkg against a local mirror of Slackware’s own system packages. It has 8 CPU cores and around 8 GB of RAM, enough to build all but the heaviest packages comfortably, and I reach it over SSH. Keeping it in its own VM means a build, a broken dependency, or a full repository regeneration never touches my daily driver: the box exists to be hammered and, if needed, thrown away and rebuilt.
Read more