rust-lang / rust-lang/rust-analyzer
Support `cargo install` and `cargo binstall` binary installation
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Manually downloading and unpacking binary from the release page is not the most "rusty" path. Rust users mostly expect cargo install rust-analyzer, or the faster binstall (which actually uses the release page automatically). Please support this mode of installation rather than the documented (but ugly):
$ mkdir -p ~/.local/bin
$ curl -L https://github.com/rust-lang/rust-analyzer/releases/latest/download/rust-analyzer-x86_64-unknown-linux-gnu.gz | gunzip -c - > ~/.local/bin/rust-analyzer
$ chmod +x ~/.local/bin/rust-analyzer
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 with the release-page artifacts and the documented binary-installation section linked in the issue, then compare the expected cargo install and cargo binstall workflows with what is published today. Done means Rust users can install rust-analyzer through both commands without the manual download, unpacking, and chmod steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100