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
Status of rustc_tools_util? #9553
Comments
use rustc_tools_util instead of vergen This avoids some 0BSD-licensed dependencies (which might or might not be a license we can use), and also just generally removes tons of dependencies and shares some code with clippy. Well, kind-of-shares -- clippy uses a path dependency (rust-lang/rust-clippy#9553) so rustc will still build this twice in the rustc repo.
I could do another clippy repo -> cratess.io sync (aka release) and we could switch clippy to also use the crates-io version while keeping the source in tree, I guess? |
Yeah I think that would be good. :) |
rustc_tools_util: bump version in anticipation of a new release cc #9553 After this is merged, I will publish the 0.2.1 version to crates.io, and make another PR that switches clippy to use the dependency from crates.io. The source can still be kept in the clippy repo though imo. This will allow miri and clippy to "share" the crate in the rustc repo once they both depend on it.
rustc_tools_util: bump version in anticipation of a new release cc #9553 After this is merged, I will publish the 0.2.1 version to crates.io, and make another PR that switches clippy to use the dependency from crates.io. The source can still be kept in the clippy repo though imo. This will allow miri and clippy to "share" the crate in the rustc repo once they both depend on it. changelog: release `rustc_tools_util` on `Crates.io`.
rustc_tool_utils: bump version in anticipation of a new release cc #9553 After this is merged, I will publish the 0.2.1 version to crates.io, and make another PR that switches clippy to use the dependency from crates.io. The source can still be kept in the clippy repo though imo. This will allow miri and clippy to "share" the crate in the rustc repo once they both depend on it. reopen of #9561 changelog: release `rustc_tools_util` on `Crates.io`.
rustc_tools_util 0.2.1 is now on crates-io 🎉 |
use rustc_tools_util dependency from crates.io instead of this repo. Fixes #9553 changelog: none
use rustc_tools_util dependency from crates.io instead of this repo. Fixes #9553 changelog: none
bump rustc_tools_util Cc rust-lang/rust-clippy#9553
Thanks. :) it is being bumped in Miri as we speak. |
we might still need a clippy sync to get rid of the path dep in the rustc repo though |
Yeah and a Miri sync needs to happen for Miri to even start using it. Short-term there might be some duplication but in the near future, after they both got synced, we'll have this code shared. :) |
vergen is causing some licensing pain in Miri, so I checked what clippy does to determine the git commit for version information. Looks like clippy has an in-tree crate
rustc_tools_util
for that. An old version of that crate exists on crates.io but clippy uses a path dependency of a more up-to-date version of that crate.Would it make sense for clippy and Miri to share that crate? clippy should then probably fetch the dependency from crates.io rather than using a path dependency, so that the dependency is actually shared in the rustc workspace.
The text was updated successfully, but these errors were encountered: