mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-09 20:26:33 +00:00
dpkg-buildpackage's debhelper sequence auto-detected the project's
Makefile and invoked 'make -j4 clean' from inside the package-build
sandbox at /tmp/infinito-nexus-debian-build. That recipe's BASH_ENV
sources scripts/meta/env/load.sh -> detect.sh, which (per the SPOT
contract) hard-fails when python3 is not yet on PATH — the package
hasn't been installed yet, so its python3 dependency isn't either.
Mirror the existing override_dh_auto_{build,test,install}: : pattern
to silence the auto-clean recurse. The .deb produced is unchanged
(no build artefacts to clean in the first place).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Packaging Layout
This directory follows the same high-level structure as package-manager:
packaging/debian/packaging/fedora/packaging/arch/
The package metadata in these folders is used to keep Infinito.Nexus host dependencies explicit and distro-specific.
scripts/install/package.sh builds and installs the local package for
the current distro (Arch, Debian/Ubuntu, Fedora), so dependency resolution is
performed by the distro package manager from package metadata.
Local Test Environment 🧪
These package definitions are required to bootstrap and run the local development/test environment reliably. 🚀
Bootstrap tooling is provided via Kevin's Package Manager: https://github.com/kevinveenbirkenbach/package-manager
Scope of declared dependencies:
- Core developer workflow (
make install,make setup) - Local/CI deployment helpers (
docker,jq,ansible,sshtooling) - Basic shell/Python helper tooling used by scripts
Optional lint/test extras are declared as Recommends/optdepends where
supported.