Binstall is a tool to fetch and install Rust-based executables as binaries. It aims to be a drop-in replacement for cargo install in most cases. Install it today with cargo install cargo-binstall, from the binaries below, or if you already have it, upgrade with cargo binstall cargo-binstall.
In this release:
- If a crate is already installed and its version is the same as would be installed, we now skip installing it, mirroring
cargo-install's behaviour. A new--forceoption lets you do it anyway. (#282) - Binstall writes to its own specific metafile format in
$CARGO_HOME/binstall/crates-v1.jsonfor global installs. This new format is better suited to binstall over the.crates2.jsondata, and lets both Binstall itself and third party tools if they so wish have access to installation information. The classic.crates.tomlis still written to too. (#252) - We now live in the cargo-bins GitHub organisation. This will let us fork some unmaintained projects that we use in here, and perhaps bring other cargo tools under this umbrella. (#251)
Other changes:
- New:
-Vto print version. (#248, #259) - New:
--quietas an alias to--log-level=off. (#281, #283) - Improved:
--manifest-pathcan take both a crate folder path and aCargo.toml's path. (#259) - Improved:
--log-level=off(or--quiet) also passes--quiettocargo-installwhen installing from source. (#281, #283) - Fix: show help when no arguments are provided. (#244, #245)
- Fix:
$CARGO_HOMEand the.crates.tomlmetafile will be created if they don't exist yet. (#267, #276) - Fix: specifying duplicate crates is now handled properly, with the latter specification being used. (#264)
- Doc: possible values of
--log-levelare listed out. (#281) - Doc: the readme has been streamlined for the use case, rather than the support case (adding binstall configuration to your crate), which has moved to its own dedicated page. (#284)
Plus many performance and CI/CD optimisations.