Repository navigation
README says which of the mac leg's inputs are not pins - #145
Open
closer-claudio wants to merge 1 commit into
Open
closer-claudio wants to merge 1 commit into
closer-claudio wants to merge 1 commit into
Conversation
The linux bullet says every input of a linux build is a pin. The macOS bullet said only that Apple's clang builds it. A reader could take the linux sentence for the whole repository. What the leg takes from the machine, read from curl-for-win at the pin and from a CI log (run 43811886931, image macos-15-arm64 20261103.629): clang and the SDK of the selected developer directory (xcrun; Xcode 16.4, MacOSX15.5.sdk there); cmake and ninja from Homebrew's directory (/opt/homebrew/bin/cmake 4.4.5, /opt/homebrew/bin/ninja), which nothing here installs. What else the build runs from /usr/bin was not traced: the sentence says only that it is the machine's, which the leg's PATH makes so (the pinned tools, then /usr/bin:/bin:/usr/sbin:/sbin, then Homebrew's directory). _ci-mac-homebrew.sh runs `brew install --quiet gnu-tar jq`, but gtar and jq on the leg's PATH are the pinned ones (forkcloser/compress, jqlang/jq), ahead of Homebrew's. Measured: the darwin curl of release v8.23.0.1 and of three CI builds kept from the audit is one sha256, f15a48ab…7515. The runner image of those four was not read, so the sentence claims no more than the comparison. Pinning cmake and ninja is #144. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Signed-off-by: closer-claudio <claudio@farcloser.world>
closer-claudio
enabled auto-merge
November 17, 2026 17:43
Contributor
Author
|
Reviewed at 741f485 |
1 similar comment
Contributor
Author
|
Reviewed at 741f485 |
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.
🎯 Why
The README's linux bullet says every input of a linux build is a pin. The macOS bullet said only that Apple's clang builds it, so a reader could take the linux sentence for the whole repository. It is not true of the mac leg.
🛠️ What
The macOS bullet now says what that leg takes from the machine that builds:
cmake, andninjawhen there is one: the machine's Homebrew's, which nothing here installs or pins;/usr/bin;gnu-tarandjq, which curl-for-win's_ci-mac-homebrew.shinstalls, are not what the build runs: the pinnedgtarandjqcome first on its PATH.🧪 How
xcrun,/opt/homebrew/bin/cmake4.4.5,/opt/homebrew/bin/ninja,gtarfrom the pinned forkcloser/compress.📝 Notes
Documentation only. Pinning
cmakeandninjais #144.