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.
3 Likes
Maybe historical reasons play a part (the same last paragraph).
This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.