CARGO-UNINSTALL(1)

✨ CARGO-UNINSTALL ✨

okay bestie, welcome to the cargo-uninstall page of the General Commands Manual 💅 this is the one where we take out the trash (respectfully) and yeet a Rust binary off your machine 🗑️✨

---

🌸 NAME 🌸

cargo-uninstall — Remove a Rust binary 🫶

---

🎀 SYNOPSIS 🎀

cargo uninstall [options] [spec…]

---

🦋 DESCRIPTION 🦋

So this command does the reverse-glow-up move: it removes a package that was installed with cargo-install(1). The spec argument is a package ID specification of the package you want to remove — go check cargo-pkgid(1) if you need the deets on how those specs work 🔍

By default, all binaries get removed for a crate, but if you're picky (and you should be, you're a main character), the --bin and --example flags let you remove only particular binaries 🎯

Now, where does it look for the install root? The installation root is determined, in order of precedence:

• the --root option 👑
• the CARGO_INSTALL_ROOT environment variable
• the install.root Cargo config value <https://doc.rust-lang.org/cargo/reference/config.html>
• the CARGO_HOME environment variable
• $HOME/.cargo

like, it goes down that list and the first one that hits, wins 🏆

---

💖 OPTIONS 💖

🌈 Install Options

• -p, --package spec… — the package you want to uninstall 🫡
• --bin name… — only uninstall the binary name ✂️
• --root dir — the directory to uninstall packages from 📁

⭐ Display Options

• -v, --verbose — use verbose output. You can pass it twice for "very verbose" output, which includes extra output such as dependency warnings and build script output 👀 May also be specified with the term.verbose config value <https://doc.rust-lang.org/cargo/reference/config.html>.
• -q, --quiet — do not print cargo log messages 🤫 May also be specified with the term.quiet config value <https://doc.rust-lang.org/cargo/reference/config.html>.
• --color when — control when colored output is used 🎨 valid values are:
  • auto (default): automatically detect if color support is available on the terminal ✨
  • always: always display colors 🌈
  • never: never display colors 💀
  • May also be specified with the term.color config value <https://doc.rust-lang.org/cargo/reference/config.html>.

💜 Common Options

• +toolchain — if Cargo has been installed with rustup, and the first argument to cargo begins with +, it will be interpreted as a rustup toolchain name (such as +stable or +nightly) 🛠️ See the rustup documentation <https://rust-lang.github.io/rustup/overrides.html> for more information about how toolchain overrides work.
• --config KEY=VALUE or PATH — overrides a Cargo configuration value. The argument should be in TOML syntax of KEY=VALUE, or provided as a path to an extra configuration file. This flag may be specified multiple times 🔁 See the command-line overrides section <https://doc.rust-lang.org/cargo/reference/config.html#command-line-overrides> for more information.
• -C PATH — changes the current working directory before executing any specified operations. This affects things like where cargo looks by default for the project manifest (Cargo.toml), as well as the directories searched for discovering .cargo/config.toml, for example 📂 This option must appear before the command name, for example cargo -C path/to/my-project build.

⚠️ heads up bestie: this option is only available on the nightly channel <https://doc.rust-lang.org/book/appendix-07-nightly-rust.html> and requires the -Z unstable-options flag to enable (see #10098 <https://github.com/rust-lang/cargo/issues/10098>) 🚨

• -h, --help — prints help information 🆘
• -Z flag — unstable (nightly-only) flags to Cargo 🌙 run cargo -Z help for details.

---

🌱 ENVIRONMENT 🌱

See the reference <https://doc.rust-lang.org/cargo/reference/environment-variables.html> for details on environment variables that Cargo reads 🌍

---

💀 EXIT STATUS 💀

• 0: Cargo succeeded ✅
• 101: Cargo failed to complete 😭

---

🍓 EXAMPLES 🍓

1. Uninstall a previously installed package.

cargo uninstall ripgrep

---

👑 SEE ALSO 👑

cargo(1), cargo-install(1) 💞

---

and that's the whole page, no cap 🧚 this was CARGO-UNINSTALL(1) from the General Commands Manual — go forth, uninstall responsibly, and remember: removing a binary is still a slay 💅✨