mirror of
https://github.com/apple/pkl.git
synced 2026-05-28 09:39:17 +02:00
Download instructions in installation docs point to invalid URL #3
Reference in New Issue
Block a user
Delete Branch "%!s()"
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?
Originally created by @jasongwartz on GitHub (Feb 3, 2024).
The docs on installation currently suggest the following instructions to download the executable:
but the URL
https://github.com/apple/pkl/releases/download/0.25.1/pkl-cli-macos-0.25.1.binis invalid:The current release page includes separate ARM vs Intel binaries, which link to eg:
https://github.com/apple/pkl/releases/download/0.25.1/pkl-macos-amd64which itself is a 302 redirect to a
https://objects.githubusercontent.com/github-production-release-asset-2e65be/745600812/...URL containing the actual binary.I was able to
curl -Lthehttps://github.com/apple/pkl/releases/download/0.25.1/pkl-macos-amd64URL to get a working binary.I'm guessing this requires a doc change in or around here: https://github.com/apple/pkl/blob/ce65290aae9c407603a26401d9ac03277bb5de7b/docs/modules/pkl-cli/pages/index.adoc?plain=1#L4 but possibly a bit of new content explaining which build to choose based on system architecture.
Happy to make a PR if it would help!
@bielikb commented on GitHub (Feb 3, 2024):
Thanks for this!
Is this binary notarized? I got an pop-up on macOS Sonoma 14.0.
@finestructure commented on GitHub (Feb 3, 2024):
Same here:
@jackkleeman commented on GitHub (Feb 3, 2024):
I generally struggle with these popups if I click to download a binary from Chrome, but it generally works fine with curl or if I run
xattr -d com.apple.quarantine ./pcl@petersid2022 commented on GitHub (Feb 3, 2024):
This is also the case for installing the Linux executable on amd64:
I was able to get the executable by using:
$ curl -L -o pkl https://github.com/apple/pkl/releases/download/0.25.1/pkl-linux-amd64@holzensp commented on GitHub (Feb 8, 2024):
Fixed by #21
@jasongwartz commented on GitHub (Feb 8, 2024):
Thanks @holzensp !