Repository navigation
Conversation
orchd 0.5 is Zig and ships as release binaries, not on crates.io, so the installer's `cargo install orchd =0.4.0` could only ever reach 0.4. It now fetches the pinned 0.5.0 release for the host, checks its sha256, and installs orchd with orch and the rootstocks beside it: orchd reads every Orchfile through `orch resolve --json`, so orch is no longer optional. A host with no orchd build (Intel macOS) gets a warning instead of a failed install, since hum never calls orchd. orchd 0.5 replaced --namespace with --grove and rejects the old flag, so every bundled hive's install now grows under `--grove hum-<hive>`. hum parses Orchfiles with the-orch 0.3. Orch 0.3 takes runtime values as ARG overrides and applies only the declared ones, so the whole environment goes in and parse_raw, which 0.3 removed, is no longer needed to find the declared ARGs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves hum onto the latest of both: orchd 0.5.0 and the-orch 0.3.0.
Installer. orchd 0.5 is Zig and ships as GitHub release binaries (it isn't on crates.io), so
cargo install orchd --version =0.4.0could only ever install 0.4../installnow downloads the pinnedv0.5.0tarball for the host, verifies its.sha256, and installsorchd,orchand theorchd-rootstock-*binaries into~/.local/binwith atomic renames.orchis required now: orchd 0.5 reads every Orchfile throughorch resolve --json. Hosts with no orchd build (only x86_64-linux, aarch64-linux and aarch64-macos have one) get a warning instead of a failed install, since hum itself never calls orchd.Hives. orchd 0.5 replaced
--namespacewith--groveand rejects the old flag (error: unexpected argument '--namespace'), so all 14 hiveinstallscripts now grow under--grove "hum-$hive". All 16 hive Orchfiles passorch validate0.3.the-orch 0.3. The only break is that
parser::parse_rawis gone. Orch 0.3 takes runtime values as ARG overrides and applies only the ARGs a file declares, soorchfile::resolvenow passes the whole environment and no longer pre-scans for declared ARGs. That's the same semantics as before, and the same resolution orchd does. There are 4 new unit tests.Verified. The installer's orchd step was run in a scratch root against the real release (installs all 5 binaries, version and API checks pass), against a tampered tarball (stops on the checksum mismatch), and against a missing release (stops on the fetch error). Temp dirs are cleaned up in every case.
cargo test -p humpasses, includingconform.README mentions of "namespace" (
hives/README.md) and the man page's binary list are left for a separate docs change.