Archived
David Heinemeier HanssonandClaude Opus 5
daf98026bc
The first version checked for pacman and refused anything else, so it would have declined to run on the actual repository host. Nothing about that host needs to be Arch: makepkg, repo-add and signing all happen inside containers. Setup now detects apt or pacman and installs the right names for each -- bsdtar is libarchive-tools on Debian and libarchive on Arch. The requirement list drops gnupg and the Arch build tools, which the host never runs directly, leaving Docker, rclone, bsdtar, jq, git and rsync. Docker is checked before being installed. A host may be running a version from Docker's own repository, and replacing that underneath a working builder would be a poor trade for consistency; setup starts it if stopped and otherwise leaves it alone. Verified both paths: apt installs the five dependencies and docker.io on a bare Ubuntu 24.04 container, and an Arch host with Docker already running is left untouched. A missing systemctl now reports that a container cannot be a repository host instead of failing on an unknown command. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>