Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid rendering a mock root package when possible #1596

Merged
merged 3 commits into from
Oct 17, 2022

Conversation

UebelAndre
Copy link
Collaborator

@UebelAndre UebelAndre commented Oct 16, 2022

The use of Cargo.lock is a relatively new feature (#1426) which did not fully account for cases where crates_repository would be consuming Cargo.lock files produced by Cargo. This change avoids adding the direct-cargo-bazel-deps target to manifests in cases where users did not use crates_repository.packages, thus allowing Cargo defined lockfiles to be usable by the repository rule.

closes #1447

Copy link
Collaborator

@illicitonion illicitonion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, thanks!

crate_universe/src/splicing/splicer.rs Outdated Show resolved Hide resolved
@UebelAndre UebelAndre enabled auto-merge (squash) October 17, 2022 14:36
@UebelAndre UebelAndre merged commit 0493b99 into bazelbuild:main Oct 17, 2022
@UebelAndre UebelAndre deleted the unnecessary branch October 17, 2022 14:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

crate_universe should not modify the manifests provided if they represent a valid cargo workspace
2 participants