Closed spitfire05 closed 1 year ago
Per manual:
If you want to do that globally, then don't have cargo-binstall in the PATH, I consider this a configuration item.
If you want to do this per-run, then do something like -r "$(command -v cargo)"
.
If you want to do this per-crate, as I assume you do in this case, then configure something, for example cargo install-update-config -v '>=0.0.0' the-crate
, which will essentially "do" nothing.
Ok, sounds reasonable. I guess this issue can be closed then.
cargo binstall
can be sometimes problematic (#213), so it'd be nice to forcecargo install-update
to usingcargo install
, even ifcargo-binstall
is inPATH
.Something along the lines of
--no-binstall
argument flag would be nice.Thoughts?