fork/cargo
git clone https://git.julia.blue/fork/cargo
f9e20ffaf
0.90.0
1CARGO-UNINSTALL(1) 2 3NAME 4 cargo-uninstall — Remove a Rust binary 5 6SYNOPSIS 7 cargo uninstall [options] [spec…] 8 9DESCRIPTION 10 This command removes a package installed with cargo-install(1). The spec 11 argument is a package ID specification of the package to remove (see 12 cargo-pkgid(1)). 13 14 By default all binaries are removed for a crate but the --bin and 15 --example flags can be used to only remove particular binaries. 16 17 The installation root is determined, in order of precedence: 18 19 o --root option 20 21 o CARGO_INSTALL_ROOT environment variable 22 23 o install.root Cargo config value 24 <https://doc.rust-lang.org/cargo/reference/config.html> 25 26 o CARGO_HOME environment variable 27 28 o $HOME/.cargo 29 30OPTIONS 31 Uninstall Options 32 -p, --package spec… 33 Package to uninstall. 34 35 --bin name… 36 Only uninstall the binary name. 37 38 --root dir 39 Directory to uninstall packages from. 40 41 Display Options 42 -v, --verbose 43 Use verbose output. May be specified twice for “very verbose” 44 output which includes extra output such as dependency warnings and 45 build script output. May also be specified with the term.verbose 46 config value 47 <https://doc.rust-lang.org/cargo/reference/config.html>. 48 49 -q, --quiet 50 Do not print cargo log messages. May also be specified with the 51 term.quiet config value 52 <https://doc.rust-lang.org/cargo/reference/config.html>. 53 54 --color when 55 Control when colored output is used. Valid values: 56 57 o auto (default): Automatically detect if color support is 58 available on the terminal. 59 60 o always: Always display colors. 61 62 o never: Never display colors. 63 64 May also be specified with the term.color config value 65 <https://doc.rust-lang.org/cargo/reference/config.html>. 66 67 Common Options 68 +toolchain 69 If Cargo has been installed with rustup, and the first argument to 70 cargo begins with +, it will be interpreted as a rustup toolchain 71 name (such as +stable or +nightly). See the rustup documentation 72 <https://rust-lang.github.io/rustup/overrides.html> for more 73 information about how toolchain overrides work. 74 75 --config KEY=VALUE or PATH 76 Overrides a Cargo configuration value. The argument should be in 77 TOML syntax of KEY=VALUE, or provided as a path to an extra 78 configuration file. This flag may be specified multiple times. See 79 the command-line overrides section 80 <https://doc.rust-lang.org/cargo/reference/config.html#command-line-overrides> 81 for more information. 82 83 -C PATH 84 Changes the current working directory before executing any specified 85 operations. This affects things like where cargo looks by default 86 for the project manifest (Cargo.toml), as well as the directories 87 searched for discovering .cargo/config.toml, for example. This 88 option must appear before the command name, for example cargo -C 89 path/to/my-project build. 90 91 This option is only available on the nightly channel 92 <https://doc.rust-lang.org/book/appendix-07-nightly-rust.html> and 93 requires the -Z unstable-options flag to enable (see #10098 94 <https://github.com/rust-lang/cargo/issues/10098>). 95 96 -h, --help 97 Prints help information. 98 99 -Z flag 100 Unstable (nightly-only) flags to Cargo. Run cargo -Z help for 101 details. 102 103ENVIRONMENT 104 See the reference 105 <https://doc.rust-lang.org/cargo/reference/environment-variables.html> 106 for details on environment variables that Cargo reads. 107 108EXIT STATUS 109 o 0: Cargo succeeded. 110 111 o 101: Cargo failed to complete. 112 113EXAMPLES 114 1. Uninstall a previously installed package. 115 116 cargo uninstall ripgrep 117 118SEE ALSO 119 cargo(1), cargo-install(1) 120