You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In your binary releases, you release binaries for amd64 and aarch64, but these are two different naming conventions, so pulling the correct binary programmatically is unnecessarily difficult.
I would recommend you use either amd64 and arm64 (the output of dpkg --print-architecture on debian) or x86_64 and aarch64 (the output of uname -m on most/all Linux machines).
In your binary releases, you release binaries for
amd64
andaarch64
, but these are two different naming conventions, so pulling the correct binary programmatically is unnecessarily difficult.I would recommend you use either
amd64
andarm64
(the output ofdpkg --print-architecture
on debian) orx86_64
andaarch64
(the output ofuname -m
on most/all Linux machines).That way people can write scripts like this:
curl -sSL -o /tmp/curl "https://github.com/moparisthebest/static-curl/releases/download/v7.87.0/curl-$(dpkg --print-architecture)"
OR
curl -sSL -o /tmp/curl "https://github.com/moparisthebest/static-curl/releases/download/v7.87.0/curl-$(uname -m)"
At the moment I have to use this:
The text was updated successfully, but these errors were encountered: