rust-lang / rust-lang/rustup

Shorten toolchain names for display when they correspond to the default architecture

Open
#351 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Rust
Stars
7k
Forks
1.1k
Avg merge
22h 40m
Merged PRs (30d)
46

Description

Here's an example of current output:

info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: syncing channel updates for 'beta-x86_64-unknown-linux-gnu'
info: syncing channel updates for 'nightly-x86_64-unknown-linux-gnu'
info: downloading component 'rustc'
info: downloading component 'rust-std'
info: downloading component 'rust-docs'
info: downloading component 'cargo'
info: installing component 'rustc'
info: installing component 'rust-std'
info: installing component 'rust-docs'
info: installing component 'cargo'
info: syncing channel updates for '1.8.0-x86_64-unknown-linux-gnu'
info: checking for self-updates
info: rustup is up to date

  stable-x86_64-unknown-linux-gnu unchanged - rustc 1.8.0 (db2939409 2016-04-11)
    beta-x86_64-unknown-linux-gnu unchanged - rustc 1.9.0-beta.1 (37a2869af 2016-04-12)
   nightly-x86_64-unknown-linux-gnu updated - rustc 1.10.0-nightly (a0c325980 2016-04-20)
   1.8.0-x86_64-unknown-linux-gnu unchanged - rustc 1.8.0 (db2939409 2016-04-11)

This is too verbose for my taste. Since these are all for the default architucture I'd rather they not mention it.

For platforms with multiple viable architectures like windows it may still be useful to indicate the target triple, so this information may be important to indicate somewhere.

I haven't convinced myself that I actually want to do this, but asked for feedback on irlo.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by locating the CLI output that formats toolchain names and determine how the default architecture is identified. Done means default-architecture toolchains display without their target triple, while platforms where the target matters retain enough target information.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.