Hi,
It's just an observation.
$ cargo install --path .
builds the newest dependencies, not the ones frozen in Cargo.lock
. How is this possible?
Hi,
It's just an observation.
$ cargo install --path .
builds the newest dependencies, not the ones frozen in Cargo.lock
. How is this possible?
Intended behavior (last paragraph before Options). I'm not sure why; seems at conflict with this reasoning.
Maybe historical reasons play a part (the same last paragraph).