diff options
| -rw-r--r-- | docs/legacy-comparison.md | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/docs/legacy-comparison.md b/docs/legacy-comparison.md index ceac1bb..344b76c 100644 --- a/docs/legacy-comparison.md +++ b/docs/legacy-comparison.md @@ -86,3 +86,22 @@ Produce a native Controller artifact in an isolated workspace, collect its companion manifest, and run `alt-controller-image compare` against the observed legacy Controller tarball. Record every semantic delta as deliberate or unresolved in this document. + +## Current native build blocker: unavailable Hasher privilege helper + +The native CLI reached its typed `HasherInstaller` boundary and invoked `hsh` +without invoking GNU Make, `mkimage`, or `mkimage-profiles`, but this host does +not permit Hasher's installed privilege helper to run. Exact command evidence: + +```text +$ ./target/release/alt-controller-image build --spec profiles/alt-controller.toml --workspace /mnt/hermes-workspace/alt-controller-native-work-20260812 --output /mnt/hermes-workspace/alt-controller-native-20260812.tar +hsh: /usr/libexec/hasher-priv/getconf.sh: cannot access getconf helper. +error: hsh exited with exit status: 1 +``` + +No workspace, tarball, or companion manifest was produced, so no native versus +legacy semantic comparison can honestly be recorded yet. The next corrective +action is to run the same native CLI build in an environment where the host's +Hasher privilege helper is usable (or have the host Hasher installation repaired), +then inspect its generated companion manifest and compare it with the observed +legacy Controller tarball. |