Use --locked in docs for how to install libcnb-cargo
#734
+2
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
By default `cargo install` will not use any lockfile in the published crate, and instead will install the latest in-range version of any transitive dependencies. By using `--locked` the lockfile will be used, ensuring a more deterministic installation. Note: Whilst this repo intentionally doesn't commit a lockfile to Git (since this is a library crate), Cargo will include one in the crate uploaded to crates.io at time of publish, so `--locked` will still work.
edmorley
added
documentation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By default
cargo installwill not use any lockfile in the published crate, and instead will install the latest in-range version of any transitive dependencies.By using
--lockedthe lockfile will be used, ensuring a more deterministic installation.Note: Whilst this repo intentionally doesn't commit a lockfile to Git (since this is a library crate), Cargo will include one in the crate uploaded to crates.io at time of publish, so
--lockedwill still work.See:
https://doc.rust-lang.org/cargo/commands/cargo-install.html#dealing-with-the-lockfile