deb,cli,test: add --mirror to build and resolve from a pinned mirror
Pinned runners (a caching proxy, a chosen mirror) must resolve every package from one base URL. 'pkh deb --mirror <url>' passes the mirror to mmdebstrap as its mirror positional, so the chroot tarball's apt sources carry it from the bootstrap on and every apt inside the build follows - no per-build source rewriting. The mirror must serve every suite and architecture the build resolves (the security pocket and, for cross builds, the target archive included); that contract is documented, not enforced. The tarball cache is keyed per mirror (a short sha prefix before the '-buildd.tar.xz' suffix prune matches): a --mirror run over a stale distro-default tarball would silently resolve from the distro, and '--incremental' records must never fork across a mirror change. The runtime source passes recognize the pinned URL as an archive source (it carries no official host for the host-based checks): the pocket pass and the universe pass treat it as the archive, and the cross setup gives it every component and suite, no arch scoping (the mirror serves every architecture by contract) and no ports entry. 'pkh test' passes no mirror: its tarballs stay distro-default.
This commit is contained in:
+7
-3
@@ -86,9 +86,13 @@ act on the package in the current directory.
|
||||
- `pkh deb` builds the binary packages in an isolated context with the
|
||||
build dependencies installed. `--ppa` (repeatable) adds dependency
|
||||
sources, `--inject <package|.deb>` preinstalls a package, and `-j`
|
||||
caps parallel jobs. `--cross` cross-compiles instead of using
|
||||
qemu-binfmt, but most packages cannot cross-compile, so prefer qemu.
|
||||
Leave `--mode` unset unless you need a specific build context.
|
||||
caps parallel jobs. `--mirror <url>` builds the chroot and resolves
|
||||
every package from that base URL (a caching proxy on a pinned runner;
|
||||
it must serve every suite and architecture the build resolves).
|
||||
`--cross`
|
||||
cross-compiles instead of using qemu-binfmt, but most packages cannot
|
||||
cross-compile, so prefer qemu. Leave `--mode` unset unless you need a
|
||||
specific build context.
|
||||
|
||||
- `pkh lint [path]` runs lintian plus the pkh-native checks. `--json`
|
||||
emits a machine-readable report and `--list-tags` prints the native
|
||||
|
||||
Reference in New Issue
Block a user