Pacman repositories configuration transition from Artix-only to mixed Arch access
0 reputation · 05 Jul 2022, 00:21 UTC
0 reputation · 05 Jul 2022, 00:21 UTC
Artix Linux maintains independent system, world, galaxy and lib32 repositories rebuilt without systemd dependencies since the 2017 fork. The distribution ships OpenRC, runit and s6 ISO editions without a project-designated default. A documented compatibility boundary exists with Arch Linux core and extra packages that assume systemd.
Enabling Arch repositories in pacman.conf is documented as unsupported because many Arch packages have hard systemd dependencies that conflict with Artix's systemd-free base. The artix-archlinux-support package provides optional Arch repository access marked as experimental, and the gremlins repository signals an ongoing transition for packages not yet ported to systemd-free alternatives. The rolling-release nature means the boundary can shift with updates.
What is the current official recommendation for using Artix repositories together with Arch Linux core and extra? Is artix-archlinux-support considered experimental or supported for production use? How does the project define the compatibility boundary for packages with hard systemd dependencies?
34275 reputation · 05 Jul 2022, 10:37 UTC
Artix does not officially recommend combining its repositories with Arch core and extra for production use. The artix-archlinux-support package is considered experimental. The project's compatibility boundary is any package that declares systemd as a runtime dependency; such packages are expected to fail or destabilize a systemd-free Artix installation.
This guidance assumes a current Artix installation with a recent pacman release and the latest artix-archlinux-support package.
Confirmed: Artix maintains independent system, world, galaxy, and lib32 repositories rebuilt without systemd. The artix-archlinux-support package provides optional Arch repository access, and the gremlins repository exists as a transitional bridge for packages not yet ported to systemd-free alternatives.
Likely explanation (not an official guarantee): Because both distributions are rolling releases, a package that previously installed cleanly on Artix can gain a hard systemd dependency in a later Arch update. This makes mixed configurations fragile over time, even if they appear stable today.
artix-archlinux-support rather than hand-editing mirror lists. It supplies the supported configuration path for Arch access./etc/pacman.conf. This prevents Arch packages from overwriting system-critical files.pacman -Si <package-name> | grep -i systemd
If systemd appears in the Depends field, treat the package as incompatible.--nodeps to force installation. Forcing past a systemd dependency can produce shared-library mismatches and segmentation faults.gremlins repository when it already contains a systemd-free build of the package you need.You can confirm repository order with:
grep -E '^\[|^Include' /etc/pacman.conf
Artix sections should be listed above any Arch sections. You can also confirm the support package is present:
pacman -Qi artix-archlinux-support
If you are trying to install a specific package rather than enable general Arch access, share the exact package name. That lets us check whether it currently declares a hard systemd dependency, which determines whether the risk is acceptable for your use case.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.