omarchy-repo
| Version | 2026.242.0000 |
| Repo | box/github.com/opencharly/layer-omarchy-base:v2026.242.0437 |
Points pacman at Omarchy’s package sources and neutralises the boot hooks a container cannot satisfy. omarchy-repo is the first thing every other Omarchy layer needs: it repoints /etc/pacman.d/mirrorlist at Omarchy’s own pinned Arch mirror snapshot, adds the [omarchy] and [multilib] repositories, imports and locally signs the Omarchy packaging key, and stops the limine alpm hooks that cannot succeed without a mounted ESP from ever being extracted. It installs no packages of its own — that is deliberate, because a candy’s plan: steps are emitted AFTER its distro: packages, so a candy that both configured pacman and installed from it would configure too late. Members that install packages require: this one instead. Verifiable on the built image: pacman resolves core/extra/multilib from an omarchy.org host, the [omarchy] repo answers, the key is locally signed, and no limine alpm hook is present on the image.
Acceptance plan
Section titled “Acceptance plan”This candy’s plan: — the runnable spec charly check executes against a live deployment. check: steps are idempotent probes; run: steps change state.
| Intent | Step |
|---|---|
run |
write a complete pacman.conf pinned to Omarchy’s package sources |
run |
import and locally sign the Omarchy packaging key |
check |
pacman resolves core from an omarchy.org mirror, not from upstream Arch |
check |
the [omarchy] repository is configured and answers |
check |
the [multilib] repository is enabled (the lib32-nvidia-* packages need it) |
check |
the Omarchy packaging key is locally signed |
check |
the omarchy package resolves from the configured repositories |
check |
no limine alpm hook was extracted onto the image |
check |
the NoExtract rules that keep those hooks off the image are configured |