Proposal

Promote riscv64gc-unknown-linux-musl from Tier 2 to Tier 2 (with Tools)

This allows a path to enable CI/CD workflows musl build outputs depending on officially published rust-lang/docker-rust alpine images.

Alpine has support for RISC-V in all Alpine release versions (3.21 3.22 3.23) named at the published output of rust-lang/docker-rust x.py however the distro itself lacks packages for rustup until recent development "edge", so there is a need for official docker images. Outside of CI/CD use there is no need as riscv64gc-unknown-linux-gnu Tier 2 (with Tools) is already official and there exists rust-lang/docker-rust trixie images. CI/CD driven workflows are increasingly the norm so let's bring riscv64gc-unknown-linux-musl up to parity with riscv64gc-unknown-linux-gnu (with Tools).

Related issues:
rust-lang/docker-rust#272
LukeMathWalker/cargo-chef#353

Mentors or Reviewers

@eshattow

Process

The main points of the Major Change Process are as follows:

• File an issue describing the proposal.
• A compiler team member who is knowledgeable in the area can second by writing @rustbot second or kickoff a team FCP with @rfcbot fcp $RESOLUTION.
  • Refer to Proposals, Approvals and Stabilization docs for when a second is sufficient, or when a full team FCP is required.
• Once an MCP is seconded, the Final Comment Period begins.
  • Final Comment Period lasts for 10 days after all outstanding concerns are solved.
  • Outstanding concerns will block the Final Comment Period from finishing. Once all concerns are resolved, the 10 day countdown is restarted.
  • If no concerns are raised after 10 days since the resolution of the last outstanding concern, the MCP is considered approved.

You can read more about Major Change Proposals on forge.