Hi,
is it intentional that cargo install --path . re-downloads all dependencies and re-builds everything instead of relying on the build artifacts in the current package directory (e.g. output of a previous cargo build --release)?
It should reuse the same cached crates as cargo build. It should also reuse the local target dir when using --path. (without --path it is intentional that a temporary target dir is used)
Okay, so this is probably.a cargo bug.