Skip to content

Conversation

@egranata
Copy link

I was not aware of cargo-binstall and assumed it to be a typo. cargo install seems to work, and cargo binstall requires an extra step, worth documenting IMHO

I was not aware of cargo-binstall and assumed it to be a typo. cargo install seems to work, and cargo binstall requires an extra step, worth documenting IMHO
@mistydemeo
Copy link
Contributor

cargo install installs from source and from non-locked dependencies (which has broken before!), so I think I'd prefer it if cargo-binstall came first. Make sense to you?

Swapped the sections for cargo-install and cargo-binstall commands.
@egranata
Copy link
Author

cargo install installs from source and from non-locked dependencies (which has broken before!), so I think I'd prefer it if cargo-binstall came first. Make sense to you?

Yeah makes sense. I have updated the PR with swapping the two. Of course, I can't seem to squash the two commits into one, so that's something you may wanna do when you merge this?

@mistydemeo
Copy link
Contributor

Actually, I just noticed the section right below this is for cargo install. I get that with binstall coming first there was some confusion around what this was meant to be - maybe we can reword the header for the cargo install section that's already there so it's clearer what it's suggesting?

#### cargo-install

```sh
cargo install cargo-dist

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cargo install --locked cargo-dist, as well as mentioning that this will install from source

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants