cargo-install--path-. rebuilds everything from scratch, what's the point to first run cargo-build-release then?
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
I built coreutils and then install it per the instructions:
cargo build --release
cargo install --path .
I then noticed the second step just recompiles everything, do I still need the first cargo-build step at all?
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 checking the installation instructions referenced in the report and compare the effects of cargo build --release and cargo install --path .. Confirm whether the install step rebuilds artifacts and whether the preceding build is needed. Done when the instructions clearly explain or remove the redundant command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100