install/launch scripts: make install target + curl-pipeable install.sh #3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "worktree-install-launch-scripts"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds two installation paths, closing out the last backlog item.
make install— developer path, builds and installs to$(go env GOPATH)/bin, no sudo.install.sh— end-user path (curl -fsSL .../install.sh | sh): detects platform, downloads + verifies the release tarball (checksum, never a silent pass on a missing SHA256SUMS entry), picks an install location (~/.local/binif writable and on PATH, else/usr/local/binvia sudo), installs the binary, and on Linux registers a.desktopmenu entry. POSIXsh/dash-compatible, no bashisms.Spec + plan went through two rounds of external review (salyut multi-model consult + a manual review) before implementation, and each of the 6 implementation tasks was independently reviewed and approved. A final whole-branch review caught one Critical finding —
--proto-redir=httpswas a silent no-op (bare protocol name defaults to curl's additive+modifier, so it restricted nothing) — fixed to--proto-redir==httpsand independently verified against a live redirect. Also fixed in the same pass:install.shwasn't wired into the release artifacts the README told users to curl,install_test.shwasn't wired into CI, and a checksum-mismatch failure discarded its own diagnostic output.Test plan
go test -race ./...— 272/272 passingsh install_test.sh— 44/44 passinginstall.sh tests (dash)step)🤖 Generated with subagent-driven development