Static

Statically linked binaries (type = static)

A static package is one ELF binary with no PT_INTERP, so it needs no libc on the host and runs on any distribution of the right architecture. It is the format to prefer whenever a program can be built as one.

Sources

• Nearly all of them come straight from an upstream release. The recipe names the asset and pins its hash, and nothing is built.

• The rest are built in pkgforge/builds, which publishes releases soarpkgs pins the same way. A package ends up there only when pinning upstream is impossible.

Build profile

For the packages we do build:

• musl, and statically linked. A dynamically linked result fails the build.

• Source pinned by commit, toolchain pinned by image digest

• LTO and PIE where the project supports them

• Prefer mimalloc over other musl allocators, since musl's own is slow enough to be noticeable (not always)

Every staged binary is checked before it is published: it is an ELF for the architecture it claims to be, it has no PT_INTERP, and it starts. Compiling is not evidence that the result works, least of all when building for an architecture the builder cannot run.

A binary that needs desktop integration, meaning a .desktop entry and an icon, is better shipped as an AppImage or onelf package.