dosbox-x

Not tracked in arch/ — plain upstream AUR package, rebuilt from a fresh clone of https://aur.archlinux.org/dosbox-x.git into /data/INSTALL/dosbox-x. See arch/scripts/install_only_packages (local-install category) and [[feedback_local_install_rebuilds]]/[[feedback_pkgrel_vs_pkgver]] for the general workflow/pkgrel conventions this follows.

arch=() – x86_64 only, on purpose

Upstream’s PKGBUILD ships arch=(i686 x86_64 aarch64). Tried adding the full oksh-style list (i486/i686/pentium4/x86_64/arm/armv6h/armv7h/ aarch64) 2026-08-14 – i486/i686/pentium4 builds in the local archlinuxaba chroots either took excessively long or effectively hung (one i486 debug rebuild was still stuck ~40 min in after finishing source download, had to be killed via machinectl terminate + kill -9 since SIGTERM alone didn’t stop the makechrootpkg/nspawn tree). User call: drop i486/i686/pentium4 entirely, don’t chase it further.

Current arch=(x86_64 arm armv6h armv7h aarch64) – only x86_64 has a local archbuild chroot, the rest are permanent SKIPs (no local archlinuxaba-<arch>-build/extra-<arch>-build), kept in the array only because upstream lists aarch64 and it’s harmless to leave the others as aspirational/no-ops. pkgrel=1.1 reflects this local deviation from upstream’s arch=().

If revisiting this: don’t just re-add i486/i686/pentium4 and try again – first find out why those chroots are slow/hang for this package specifically (a huge C++ codebase with mesa/ffmpeg deps, possibly emulation overhead building x86-32 code, or a genuine hang worth reporting) before spending build time on it again.

2026-08-14 build

Published x86_64 2026.08.02-1.1 (dosbox-x + dosbox-x-debug).