Correct way to package this in distributions
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
What is the correct way to package rustup for shipping with linux distributions? When we just install the compiled rustup-init as /usr/bin/rustup it does not seem to put anything into ~/.cargo/bin. However, when we install it as /usr/bin/rustup-init, the users will just have to run rustup-init every time the package gets updated in order to get the correct version installed into their ~/.cargo/bin. So what is the correct way to do things, i.e. how can I get rustup to install symlinks into ~/.cargo/bin correctly (hardlinks won't probably work since it's a common pattern that /home and /usr reside on different file systems).
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 reviewing how rustup-init and /usr/bin/rustup are currently expected to behave when packaged for Linux distributions, including the relationship to ~/.cargo/bin. Confirm the supported packaging approach and document how users can obtain the correct links after package updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100