The command cargo install-update doesn't display or handle crates installed from sparsed-index source/registry (apart from crates.io which is handled differently throughout its source code). It therefore also re-installs for cargo install-update -i xyz even if crate xyz has already been installed.
This affects configurations (~/.cargo/config.toml) akin to
The command
cargo install-update
doesn't display or handle crates installed from sparsed-index source/registry (apart from crates.io which is handled differently throughout its source code). It therefore also re-installs forcargo install-update -i xyz
even if crate xyz has already been installed.This affects configurations (~/.cargo/config.toml) akin to
which has become a current default for Jfrog Artifactory package registries.
The relevant code has been identified and a pull request will follow shortly.