Exract manifest handling into its own crate
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
The build-manifest tool inside rust-lang/rust is responsible for creating manifests, and the manifest module in rustup-dist is responsible for reading and validating manifests. There have already been bugs where manifests produced by the Rust build system failed to validate. It would be preferable if the code was in a single crate and shared between the two projects.
Extract manifest.rs into its own crate, then plug that crate back into rustup, and into build-manifest. Modify build-manifest to run the validate method before writing the manifest. Extract manifest-specific tests as well. Look for other code to share between them.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the manifest module in rustup-dist and the build-manifest tool in rust-lang/rust, then inspect the manifest-specific tests and the existing validate method. Extract the shared manifest handling into a crate, integrate it with both consumers, and verify that build-manifest validates manifests before writing them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, release
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100