Closed cyqsimon closed 3 years ago
I am fully aware of the binaries provided by http and why they are so, considering I wrote it lol
Can you try the current master
branch (at least 2e76d1dc86f3266a372aefcdaea63dc5be49dbcb)? Running cargo install-update-config --respect-binaries https
should limit the binaries to the ones already installed on updates.
Oh lmao. Didn't realise you are in charge here as well. Will try it after work.
Apologies for the delay. Just got the time to test the feature. Working as intended.
Pog. Released in v7.0.0
I have the
https
package installed on my system, which installs two executables by default -http
andhttplz
. In fact they are completely identical, andhttp
is only there because people complained that the name is too generic so they changed it tohttplz
but kepthttp
for backwards compatibility.Anyhow, I install this package via
cargo install https --bin httplz
to select only one binary. However when I runcargo install-update -a
, the old binary selection is not respected. Instead, I get both binaries instead. So I have to manually runcargo uninstall https --bin http
every single time.It's only a minor annoyance for me but for someone else who might only want to use a few binaries out of a very big crate, this could become unacceptable.
Therefore my request is that
cargo-update
should first fetch the list of installed binaries (via something likecargo install --list
) and only update those. Or better, provide a flag to set this behaviour.