CARGO-UNINSTALL(1)

CARGO-UNINSTALL(1) 💖

okay bestie, welcome to the General Commands Manual page for cargo-uninstall — this is the glow-up guide for yeeting a Rust binary off your machine, no cap ✨

---

✨ NAME ✨

cargo-uninstall — Remove a Rust binary 🗑️💅

---

🦋 SYNOPSIS 🦋

cargo uninstall [options] [spec…]

---

💜 DESCRIPTION 💜

so basically, this command removes a package that you installed earlier with cargo-install(1). like, it's the undo button, the "we don't talk about bruno" button, the it's not you it's me button 🫶

the spec argument is a package ID specification of the package you wanna remove — see cargo-pkgid(1) if you need the full lore on how those specs work, iykyk 📖✨

by default, all binaries are removed for a crate. but if you're feeling selective (main character energy), the --bin and --example flags let you only remove particular binaries 🎯

now, where does cargo actually go looking for stuff to uninstall? the installation root is determined in order of precedence, so first one that hits wins:

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

order matters fr fr, it checks them top to bottom 👑

---

🌸 OPTIONS 🌸

🎀 Uninstall Options 🎀

• -p, --package spec… — the package to uninstall 💖
• --bin name… — only uninstall the binary name. picky, and honestly? valid 🍓
• --root dir — the directory to uninstall packages from 📁

🌈 Display Options 🌈

• -v, --verbose — use verbose output. and yes bestie, you can specify it twice for "very verbose" output, which throws in extra stuff like 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:
  • 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'll be interpreted as a rustup toolchain name (like +stable or +nightly) 🛠️ see the rustup documentation — https://rust-lang.github.io/rustup/overrides.html — for more info 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 info.
• -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.

⚠️ 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). so if you're on stable, sorry babe, not today 😭

• -h, --help — prints help information 💬 the classic, the icon, the moment.
• -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. slay ✨
• 101: Cargo failed to complete. it's giving not slay 💀

---

🍓 EXAMPLES 🍓

1. Uninstall a previously installed package.

cargo uninstall ripgrep

and that's it, bye ripgrep, it was real 🫶

---

💫 SEE ALSO 💫

cargo(1), cargo-install(1)

---

k bye bestie, go forth and uninstall responsibly 💖 this was CARGO-UNINSTALL(1) from the General Commands Manual — same title top and bottom, that's just how manpages do 🎀