Handling of deprecated binaries in crates.toml

[letheed]

cargo-edit 0.1.6 used to provide the following binaries: ["cargo-add", "cargo-list", "cargo-rm"].
cargo-edit 0.2.0 now provides ["cargo-add", "cargo-rm", "cargo-upgrade"].

I updated cargo-edit by running cargo install-update cargo-edit[edited typo] which in turn ran cargo install -f cargo-edit. Now, I have with the following in my .crates.toml:

"cargo-edit 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = ["cargo-list"]
"cargo-edit 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = ["cargo-add", "cargo-rm", "cargo-upgrade"]

Is that the expected behavior? This seems to leave 0.1.6 in an inconsistent state since cargo-add and cargo-rm are now v0.2.0 when cargo-list is still v0.1.6.

Is this acceptable and can this be improved, or are subcommands like cargo-install-update expected to handle this?

[nabijaczleweli]

(dropping by to say that it's cargo install-update, not cargo update-installed)

[alexcrichton]

I think this is semi-expected today but probably not the right behavior, we should likely just uninstall all binaries associated with a crate rather than just the subset being overridden.