diff options
| author | Danilo M. <danix@danix.xyz> | 2026-06-25 10:11:05 +0200 |
|---|---|---|
| committer | Danilo M. <danix@danix.xyz> | 2026-06-25 10:11:05 +0200 |
| commit | ad8eeffef44ebadf2368a191c00ab9031362aa9e (patch) | |
| tree | dd0628a649d5170499551f44f7669ef08a3e24ff /README.md | |
| parent | 02c82b8ad41167ac46d9b0b467b5eef39dc70d37 (diff) | |
| download | sbo-batch-tester-ad8eeffef44ebadf2368a191c00ab9031362aa9e.tar.gz sbo-batch-tester-ad8eeffef44ebadf2368a191c00ab9031362aa9e.zip | |
Lint built target package with sbopkglint
After a target builds successfully, run sbopkglint (from
system/sbo-maintainer-tools) against the built .txz as a final
check. Host-side, target only, fail-soft: skips with a note if the
tool is absent and never changes the SUCCESS status. The one-line
result is color-coded (green clean, red findings); on findings the
full output is echoed to the screen and the package log. Verified
live on buildsystem with feh.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 17 |
1 files changed, 17 insertions, 0 deletions
@@ -50,6 +50,10 @@ that is `/root/.config/sbo-batch-tester/config`). Override the path with the Also: run as root (overlay + chroot require it). +Optional: install `system/sbo-maintainer-tools` to get `sbopkglint`. If present, +the target's built package is linted as a final check (see below). If absent, the +step is skipped with a one-line note. + ## Populating SLACKWARE_BASE Populate from the NFS mirror with the FULL package set, not a minimal install. @@ -150,6 +154,19 @@ Packages whose REQUIRES carry `%README%` are flagged in the summary as a reminder to check manual/optional configuration steps. `%README%` is not a package and is skipped for build ordering. +## Package lint (sbopkglint) + +After a target builds successfully, if `sbopkglint` (from +`system/sbo-maintainer-tools`) is on the host PATH, the harness runs it against +the target's built `.txz` as a final verification. It catches common SBo policy +problems that a clean build does not (ownership, doc-dir contents, slack-desc, +etc). The check is host-side, target only (dependencies are vetted SBo packages +and would only add noise), and fail-soft: findings are reported to the screen +and the package log but never change the build's `SUCCESS` status, and a missing +tool just prints a skip note. The one-line result is color-coded (green `clean`, +red `findings`); on findings the full sbopkglint output is also printed to the +screen, indented, with a complete copy in the per-package log. + ## Logs Written outside the overlay so they survive teardown, under `LOG_ROOT`: |