Command-line-friendly way to rustup on windows
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
Projects that are building on windows in CI need a one-liner to install and run the rustup.
The same way it works on unix and mac.
Example of a script that people use at the moment in CI https://github.com/rust-onig/rust-onig/blob/68393b487c679c789ee8a762e77f568e75a3128a/appveyor_rust_install.ps1
This script is not a very good because it uses appveyor-specific calls.
A better one may look something like
$client = new-object System.Net.WebClient
$client.DownloadFile('https://win.rustup.rs', "$pwd\rustup-init.exe")
.\rustup-init.exe
This is a powershell script, powershell ships inbox on all windows machines.
Bells and whisles to pass channels and other parameters could be added.
By hosting it on the ps1.rustup.rs, there would be a simple copy-pastable one-liner, like in choco https://chocolatey.org/install
It can be then put on https://rustup.rs/ under windows tab.
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 comparing the referenced AppVeyor PowerShell installer with the proposed rustup-init.exe download flow. Then inspect rustup.rs, especially the Windows tab, to determine where the copy-pastable command would be added. Done means Windows CI users have a documented one-liner that installs and runs rustup with optional parameters without AppVeyor-specific calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, rust
- Domain
- cli, operating-systems, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100