`cargo binstall` doesn't download from GitHub releases

[eirnym]

Description

At the moment of writing cargo binstall (1.16.6) doesn't undestand release file name scheme, thus uses QuickInstall source. Could you please make filename scheme compatible with cargo binstall or update cargo binstall to match yours?

[epage]

It would help if you gave more specifics about the problems you have.

[eirnym]

When I run cargo binstall typos-cli --verbose typos-cli, the tool tires to download release binaries from GitHub releases using various patterns, but all known patterns don't match and it fallbacks to QuickInstall repo.

I prefer that cargo binstall would download from this repository instead of QuickInstall

[eirnym]

cli output is too long to include in here

[GideonBear]

This is not because only a musl build is available, because:

Binstall is able to look for binaries for several targets, installing the first one it finds in the order the targets were given. For example, on a 64-bit glibc Linux distribution, the default is to look first for a x86_64-unknown-linux-gnu binary, then for a x86_64-unknown-linux-musl binary. However, on a musl system, the gnu version will not be considered.

I believe the cause to be the .tar.gz file being named with typos- and not typos-cli-.
For example, Topgrade uses the same naming scheme, except the crate name matches the name of the archive.
Workaround:

$ cargo binstall typos-cli
[...]
 WARN The package typos-cli v1.42.0 (x86_64-unknown-linux-gnu) has been downloaded from third-party source QuickInstall
[...]
$ cargo binstall typos-cli --pkg-url="{ repo }/releases/download/v{ version }/typos-v{ version }-{ target }.{ archive-format }"
[...]
 WARN The package typos-cli v1.42.0 (x86_64-unknown-linux-musl) has been downloaded from github.com
[...]

[GideonBear]

Alternatively to changing the archive name, we could also add the format (specified in --pkg-url above) in Cargo.toml: https://github.com/cargo-bins/cargo-binstall/blob/main/SUPPORT.md

[eirnym]

Alternatively package.metadata.binstall could be provided to guide binstall of naming convention as described here