Skip to content

Commit b08e4cb

Browse files
committed
Auto merge of #6823 - spl:clarify-install-path, r=alexcrichton
Clarify docs of install without <crate> This is an attempt to clarify the documentation of `install` without `<crate>`. I found it confusing trying to determine to which behavior “this” referred as well as whether “supported” meant “maintained” or “worked.”
2 parents 6f3e9c3 + 3ed4ad8 commit b08e4cb

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

src/bin/cargo/commands/install.rs

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -89,9 +89,8 @@ enables overwriting existing binaries. Thus you can reinstall a crate with
8989
`cargo install --force <crate>`.
9090
9191
Omitting the <crate> specification entirely will install the crate in the
92-
current directory. That is, `install` is equivalent to the more explicit
93-
`install --path .`. This behaviour is deprecated, and no longer supported as
94-
of the Rust 2018 edition.
92+
current directory. This behaviour is deprecated, and it no longer works in the
93+
Rust 2018 edition. Use the more explicit `install --path .` instead.
9594
9695
If the source is crates.io or `--git` then by default the crate will be built
9796
in a temporary target directory. To avoid this, the target directory can be

0 commit comments

Comments
 (0)