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.
When doing local development, users may wish to specify many
path
dependencies that all live in the same local directory. If that local
directory is not a short distance from the
Cargo.toml
, this can getunwieldy.
This patch introduces the notion of path "prefixes", which are defined
in
.cargo/config.toml
:Which can then be used as the root for path dependencies. For example:
would fetch
foo
from/home/jon/dev/rust/foo
,bar
from/home/jon/dev/rust/bar
, andbaz
from/home/jon/dev/rust/ws/baz
.This feature also serves as a convenient way for external build systems
to mask build-dependent paths from the user. Consider a build system
that vendors first-party dependencies into
Instead of requiring users to hard-code that path, or the relative
equivalent, into their
Cargo.toml
, the build-system can insteadproduce a project-local
.cargo/config.toml
that defines that path asbase.vendored
, and the user can then use vendored dependencies using