do not edit — generated by btf.
git.druid.rocksindexdruid520mpdocs/reference/commands/remove.btft

docs/reference/commands/remove.btft


[table class="topnav"]
[tr]
[td class="logotab"]mp[e]
[td][see name="index"]index[e][e]
[td][see name="guide/index"]guide[e][e]
[td][see name="reference/index"]reference[e][e]
[e]
[e]
 
[h1]mp remove[e]
 
[h2]synopsis[e]
 
[code]
mp remove [--force] <pkg|world|@set> ...
[e]
 
[h2]description[e]
 
removes one or more installed packages: runs the port's [code]remove:[e] phase (or legacy [code]del.sh[e]), then sweeps every file its manifest lists (unless the port sets [code]pkg_manifest_cleanup="no"[e] -- see [see name="reference/hooks"]reference/hooks[e] and [see name="reference/mp-conf-example"]mp.conf.example[e] for why a self-hosting-critical package needs that).
 
package-name expansion is the same as everywhere else ([code]world[e], [code]@set[e], a bare name); a bare name for a statically slotted package resolves to whichever one slot is actually installed, same fallback [see name="reference/commands/why"]why[e]/[see name="reference/commands/tree"]tree[e]/[see name="reference/commands/update"]update[e]/[see name="reference/commands/prune"]prune[e] all use.
 
removal does not check whether something else still depends on the package -- use [see name="reference/commands/revdep"]revdep[e] first if that matters, or let [see name="reference/commands/prune"]prune[e] handle "installed only because something else needed it" removals automatically instead.
 
[h2]options[e]
 
[code]--force[e], [code]--config=<file>[e], [code]--sysroot=<name>[e] -- see [see name="reference/config"]reference/config[e].
 
[h2]examples[e]
 
[code]
mp remove figlet
mp revdep figlet          # check first: who links against it
mp remove figlet oldstuff
[e]
 
[h2]see also[e]
 
[see name="reference/commands/prune"]prune[e], [see name="reference/commands/revdep"]revdep[e], [see name="reference/commands/files"]files[e], [see name="reference/commands/hold"]hold[e] (blocks removal persistently).
powered by btf.