Arch packages (pacman)
System packages for Arch-family Linux (Arch, Manjaro, EndeavourOS, ...).
[bootstrap.packages]
"pacman:openssl" = "latest"
"pacman:base-devel" = "latest"
"pacman:libreoffice-fresh" = { state = "absent" }For a rolling-release workstation, keep the whole system current using Arch's supported full-system upgrade workflow before adding packages. mise's scoped upgrade command is not a replacement for that workflow; see the partial-upgrade limitation below.
Preview and apply
mise bootstrap packages status
mise bootstrap packages apply --manager pacman --dry-run
mise bootstrap packages apply --manager pacmanThese commands use the active [bootstrap.packages] declarations. To add and install a package together, use mise bootstrap packages use pacman:openssl. The manager must be available on the host; an explicit --manager pacman fails when it is unavailable.
Behavior
- Package state is checked with
pacman -Qandpacman -T(read-only, never elevates). An installed package that satisfies the requested name throughProvidescounts as installed. - Missing packages are installed with
pacman -S --noconfirm --needed, elevated with sudo when necessary (see sudo).--neededmakes installs idempotent. - Packages declared with
state = "absent"are removed withpacman -R --noconfirm. Removal is based on pacman's installed package database, so it works the same for official Arch packages and packages from configured third-party repositories such as the Omarchy Package Repository. mise does not cascade to dependents or remove orphaned dependencies. - If
/var/lib/pacman/synccontains no databases (fresh containers), mise runspacman -Syautomatically before installing. Force a refresh withmise bootstrap packages apply --update. mise bootstrap packages upgraderunspacman -Syand then upgrades only the configured packages. Requests satisfied throughProvidesare skipped to avoid replacing the installed provider. Arch officially supports only full-system upgrades (pacman -Syu) — upgrading individual packages is a partial upgrade, so prefer runningpacman -Syuyourself on a rolling-release system.
WARNING
Arch repositories only carry the latest version of each package, so pacman entries cannot be installed at a pinned version — mise bootstrap packages apply skips pinned entries with a warning, though mise bootstrap packages status still reports a version mismatch for them. Declare packages that must be built from the Arch User Repository with the separate aur: manager.