diff options
| author | Craig Jennings <c@cjennings.net> | 2026-08-20 06:01:20 -0700 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-08-20 06:01:20 -0700 |
| commit | c588b0841df440e1a5290c7150ee245f90d1788e (patch) | |
| tree | b3628198ea4bd8869ca3e4f252dd59764bca3fbf /docs/2026-06-10-tool-evaluation-criteria.org | |
| parent | f876a717af9ae644320f014e30866bb919fcfe4e (diff) | |
| download | archsetup-c588b0841df440e1a5290c7150ee245f90d1788e.tar.gz archsetup-c588b0841df440e1a5290c7150ee245f90d1788e.zip | |
feat(post-rebuild-check): let a machine declare which units it means to leave disabled
Check 2 treats "enabled" as a proxy for "will actually run", and the proxy is wrong for a unit nobody intends to enable on that box. velox has four: geoclue-agent is redundant because hyprland's exec-once starts the binary itself, emacs is started on demand by emacsclient, obs-record-watchdog only matters while recording, and obsbot-wb-guard needs an OBSBOT the laptop doesn't have. All four reported at every run.
Four permanent lines in front of every real finding teach me to skim the output, which is the argument check 4 already makes about CLAUDE.md. On velox this takes the run from 8 findings to 4.
The list is machine-local, read from $XDG_CONFIG_HOME/post-rebuild-check/units-expected-disabled. It can't live in the unit file, because obsbot-wb-guard is correctly enabled on ratio. One unit, a different right answer per machine.
An entry whose unit is enabled after all is reported too. The main loop can't catch that, since it skips any state that isn't disabled or linked, so the list gets its own pass. Without it a stale exemption sits there suppressing nothing, and the list becomes somewhere real findings go to die.
The exemption is tested last, so it never hides the dangling-symlink finding decided on the filesystem above it.
Diffstat (limited to 'docs/2026-06-10-tool-evaluation-criteria.org')
0 files changed, 0 insertions, 0 deletions
