Closed melMass closed 2 months ago
I think calling cargo-binstall
instead of cargo binstall
in this action would work?
I thought cargo-binstall requires cargo, so I wrote docs as follows:
https://github.com/taiki-e/install-action#compatibility
at least the following tools are required:
- bash
- cargo (if you use cargo-binstall fallback)
But if cargo-binstall works without cargo, it would make sense to call it without cargo as we already do with other cargo-*
tools.
If cargo-binstall does not work without cargo and you have strong reservations about installing cargo, I think it would be best to add the tools you want to use to this action as officially supported tools.
Filed https://github.com/taiki-e/install-action/pull/501 to fix this.
Fixed in 2.34.0. Thanks @melMass for the report!
That was fast. Thanks a lot!
But if cargo-binstall works without cargo, it would make sense to call it without cargo as we already do with other cargo-* tools.
It doesn't need cargo, it's designed to be standalone, and have no runtime dependencies (on musl also no libc/lld)
Hi,
In a CI where I don't need Rust but some rust binaries I wanted to use this action but following the fallback approach, i.e:
It fails as it tries to call
cargo binstall
and notcargo-binstall
. I tried the "official" binstall action but it doesn't add the bin path to PATH and I couldn't find a reliable way to do it cross runners.Is there a better way?
Thanks