Custom component registry
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
Desired feature: The ability to keep third-party toolchain-specific binaries up to date.
Proposed interface:
rustup channel add <source>
rustup component add my_custom_component
Possible implementation:
channel add <url> downloads <channel>-channel-manifest.toml from the url for the current toolchain.
component add first checks the toolchain's multirust-channel-manifest and then consults the custom channel manifests.
Concrete use-case:
Binaries installed via cargo that require #![feature(rustc_private] fail with a spectacular dynamic linking error when the rustc version changes. It'd be great to keep these up-to-date in the same way that clippy, rustfmt, et al. are.
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 by reading the existing rustup channel add and rustup component add command handling and how channel manifests are consulted. The feature should support custom channel sources and keep custom components aligned with the current toolchain, including the stated rustc_private use case; verify behavior with tests for both commands and manifest lookup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100