🧬 Supported architectures

📋 The matrix

Rows are apt package names, not tool names, because that is what you type: a tool that ships more than one package (bun-one, zig-oldstable, a -dbgsym) gets a row per package, with the tool it belongs to in the second column. Sorted by package name.

🔍 How to read it

The middle state is the one worth understanding. riscv64 is not a thing Debian 12 Bookworm or Ubuntu 22.04 Jammy can be built against here, so a package like starship or uv ships riscv64 on the newer suites and not on the older ones. Collapsing that into a single yes would tell a Bookworm reader something untrue, and collapsing it into a no would hide a build that exists, so the cell names the suites instead.

🧭 Why a package might be missing an architecture

• Upstream publishes no binary for it. Most packages here repackage the release artefacts the upstream project builds. Where upstream ships amd64 only, so does this repository: that is why bun is amd64 alone.
• The suite predates the architecture. riscv64 is only carried on the newer Debian and Ubuntu suites, which is where the partial cells come from.
• The build needs a newer glibc than the suite has. This removes whole suites rather than architectures, so it shows up as a package that is simply absent from Bookworm or Jammy rather than as an empty cell.

If a tool you need is missing an architecture you use, say so in the Discord. Where upstream publishes a binary for it, adding it is usually a small change to that tool's packaging repository. How packages are built →

← Back to the main page