curl | sh makes Rust look bad
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- documentation
Research direction
Start at the Rust installation documentation and review how macOS and Linux installation are currently presented. Update the recommendations to include rustup’s .pkg format for macOS and separate downloading the Linux script from running it; done means both less controversial paths are clearly documented.
Written by the indexing model from the issue text.
Description
curl | sh has a horrible reputation of being a dangerous hack, and this is how Rust presents itself to new users.
I know Rustup's implementation is safe. I get it's absurd to worry about being unable to audit a 300-line script when installing 10 million lines of compiled code.
But still, when I tell people to install Rust, I have to start by debunking conspiracy theories and defend something that has a toxic reputation. It's really a bad start when new users feel unsafe, and have to do something "against best practices".
Please, recommend less controversial installation methods:
-
For macOS recommend rustup in .pkg format.
-
For Linux at least display the script in two lines :)
curl -o install https://sh.rustup.rs
sh install
Copied directly from @kornelski, and no less relevant today than it was years ago.
- Dominant language
- Rust
- Stars
- 120k
- Forks
- 18.7k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 550
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from rust-lang/rust
-
relnotes relnotes-needs-review relnotes-tracking-issue T-compiler T-lang T-rustfmt
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
A-run-make A-testsuite relnotes relnotes-needs-review relnotes-tracking-issue T-bootstrap T-cargo T-compiler
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
relnotes relnotes-needs-review relnotes-tracking-issue T-libs
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
innvalid `invalid_nan_comparisons breaks`: no method named `is_nan` found for reference `&{float}`Possibly taken @caelyreth claimed this 4 days ago. OpenA-diagnostics A-floating-point A-suggestion-diagnostics C-bug D-invalid-suggestion L-invalid_nan_comparisons T-compiler
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
relnotes relnotes-needs-review relnotes-tracking-issue T-compiler T-libs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
rust-lang/rust#163875 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
area:ecosystem documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Chelis-Lang/chelis#3866 ·
Maintainers usually reply within 1 day
-
bug documentation sev-0
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
dekobon/big-code-analysis#1620 ·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100