"Cargo install" should provide download binaries only from crate.io if availibale rather than build these binaries every time when calling cargo install

[wy6688]

Problem

"Cargo install" should provide download binaries only from crate.io if availibale rather than build these binaries every time when calling cargo install. since the build process in local computer is very slow, especially when call "cargo install" when build a docker containers.

Proposed Solution

provide "cargo install --no-locall-build" or "cargo install --download_binaries_only"

Notes

No response

[wy6688]

Since the "cargo install" only installed tools used by local env, download these tools is lots of faster than build them locally.
In my docker enviroments, every time when I rebuild my dev container, over 99.99999% times is on "cargo install", over 20 minutes.

[epage]

An important first step in consideration is #7169 as we would effectively be locking in the lockfile otherwise.

We also have #5931 which would help some but not too much until the follow up idea of a remote cache support and then that could be a potential way of solving this problem.

There is also the question of what the role of cargo install should be. Personally, I don't think we should grow the scope to pull in more general purpose binary package distribution needs (e.g. #2729) and which inclines me to say we shouldn't have a special built built-in pre-built bin install system.

In terms of third-party efforts in this direction, see https://crates.io/crates/cargo-binstall

[wy6688]

Thank you so much for your fast reply and help.
The cargo-binstall do works perfect for my case, greatly reduced my dev container rebuild time.
It maybe best integrate or merge this feature as build-in, so as avoid to compile and build cargo-binstall tools also.