-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Manifests in rustc-src distributed package are not valid any more #138304
Comments
... Yeah. I'll post a revert to buy time to reconsider this. |
Revert <rust-lang#138084> to buy time to consider options that avoids breaking downstream usages of cargo on distributed `rustc-src` artifacts, where such cargo invocations fail due to inability to inherit `lints` from workspace root manifest's `workspace.lints` (this is only valid for the source rust-lang/rust workspace, but not really the distributed `rustc-src` artifacts). This breakage was reported in <rust-lang#138304>. This reverts commit 48caf81, reversing changes made to c666287.
Why is the root Cargo.toml not included in rustc-src? Is it because rustc-src doesn't contain other projects that are part of the root workspace too? |
I suspect this is the case if |
yeah the root |
…=Noratrieb Revert "Use workspace lints for crates in `compiler/` rust-lang#138084" Revert <rust-lang#138084> to buy time to consider options that avoids breaking downstream usages of cargo on distributed `rustc-src` artifacts, where such cargo invocations fail due to inability to inherit `lints` from workspace root manifest's `workspace.lints` (this is only valid for the source rust-lang/rust workspace, but not really the distributed `rustc-src` artifacts). The problem is that the `rustc-src` component doesn't include the root `Cargo.toml` manifest. This breakage was reported in rust-lang#138304. This reverts commit 48caf81, reversing changes made to c666287. cc `@RalfJung` r? `@nnethercote` (sorry, I didn't consider this being a thing 💀)
In addition to lints, workspace dependencies may be nice in the future. If fixing up the workspace Cargo.toml before release is an option, that seems like a nice way forward so we keep its advantages. It may also be possible to split the workspaces based on what gets distributed, like Bjorn did for library/ somewhat recently. |
Rollup merge of rust-lang#138306 - jieyouxu:revert-workspace-lints, r=Noratrieb Revert "Use workspace lints for crates in `compiler/` rust-lang#138084" Revert <rust-lang#138084> to buy time to consider options that avoids breaking downstream usages of cargo on distributed `rustc-src` artifacts, where such cargo invocations fail due to inability to inherit `lints` from workspace root manifest's `workspace.lints` (this is only valid for the source rust-lang/rust workspace, but not really the distributed `rustc-src` artifacts). The problem is that the `rustc-src` component doesn't include the root `Cargo.toml` manifest. This breakage was reported in rust-lang#138304. This reverts commit 48caf81, reversing changes made to c666287. cc `@RalfJung` r? `@nnethercote` (sorry, I didn't consider this being a thing 💀)
The revert landed so closing this specific instance as fixed. However, this is one of those general #136822 problems. And yeah, having multiple dist components that serve different consumers but that we don't really test is really not great. |
The Miri build against latest rustc master is failing with the following error:
The problem is that that
Cargo.toml
file appears inside a workspace in this repo, but not in rustc-src. So this breaks every useage of cargo on the distributed rustc-src artifacts.This is caused by #138084. Cc @nnethercote @jieyouxu. I think that PR should be reverted to minimize downstream breakage while we consider our options.
The text was updated successfully, but these errors were encountered: