mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-09 12:17:13 +00:00
kevinveenbirkenbachandClaude Opus 5
535ffd9964
The policy admits an Exception comment when it names a concrete trip-wire. Neither of these did. The compose one argued why the task delegates over query(node_hosts) instead of guarding on not IS_STACK_HOST; the loop with run_once already says every node, and the guard it warns about is not in the file to be misread. The dnf-mirrors one explained why the SIG repository needs its own sed, directly above a sed whose own path carries SIGs/<stream>/extras/<arch>/extras-common. Both came from155b35ec54and59840c3362earlier today. The reasoning stays in those commit messages, which is where it belongs. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Install Scripts
This directory contains scripts that install and bootstrap host-side tooling used by the project.
- 📦 Install Python, Ansible, and lint dependencies for supported environments
- 🐧 Install ad-hoc APT packages for CI and workflow jobs via
apt.sh - 📦 Build and install distro package metadata via
package.sh(Arch/Debian/Ubuntu/Fedora) - 🪞 Point an Ubuntu image's apt sources at
INFINITO_APT_UBUNTU_MIRRORSviaapt-mirrors.sh, run first in the image build: apt tries the mirrors in list order and moves on when one fails or stays silent for 10 s; images of other distros are left untouched - 🏖️ Install OS-level Claude Code sandbox dependencies (
bubblewrap,socat) viasandbox.sh, covering Debian, Ubuntu, Fedora, CentOS/RHEL/Rocky/Alma, and Arch; also exposed asmake install-agent - 🧊 Install the ext4, btrfs and zfs userlands via
filesystem.sh(distro packages, EPEL for btrfs on CentOS, the AUR PKGBUILD for zfs on Arch, the zfsonlinux repository on Fedora/CentOS); the kernel side comes from the host - 🐍 Bootstrap virtual environments and editable project dependencies
- 🛠️ Keep host preparation separate from lint, build, and test execution
The scope of this folder is installation and bootstrap. Lint execution, build workflows, and test orchestration should stay in their dedicated script directories.