docs/reference/commands/manifest_clean.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/commands/index"]reference[e][e]
[e]
[e]
 
[h1]mp manifest_clean[e]
 
[h2]synopsis[e]
 
[code]
mp manifest_clean <pkg> ...
[e]
 
[h2]description[e]
 
deletes every file an installed package's own manifest lists, directly, without running the port's own [code]remove:[e] phase (or legacy [code]del.sh[e]) and without touching its db entry -- the package still shows as installed afterward. distinct from [see name="reference/commands/remove"]remove[e] (which does all of that, PLUS this) and from [see name="reference/commands/clean"]clean[e] (which only ever clears a port's stage/build directory, never a live installed file).
 
exists for the narrower case: a package whose db/manifest and on-disk files have drifted out of sync, and the fastest fix is "just delete what the manifest says is there" rather than a full uninstall/reinstall cycle.
 
prints the full, resolved file list before asking [code][y/N] continue?[e] -- [code]--yes[e]/[code]-y[e] skips the prompt, same as every other state-changing command.
 
deliberately does NOT consult [code]pkg_manifest_cleanup[e]: that flag exists to stop mp's own automatic internal sweep (fired as a side effect of [code]reinstall[e]/[code]remove[e]) from fighting a port that manages its own complete removal, or from deleting files a port deliberately leaves behind (meta/mp itself). this command is a direct, explicitly-named, manually-confirmed action in the first place -- the file list shown before the prompt is the real safety gate.
 
a bare name for a statically slotted package resolves to whichever slot is actually installed, same fallback [see name="reference/commands/why"]why[e]/[see name="reference/commands/tree"]tree[e]/[see name="reference/commands/files"]files[e] all use. a package with no manifest at all (not installed, or installed before manifest tracking existed) prints a note and moves on rather than erroring.
 
[h2]examples[e]
 
[code]
mp manifest_clean figlet
figlet:
  /usr/local/bin/figlet
  /usr/local/share/figlet/fonts/standard.flf
manifest_clean: delete the 2 file(s) listed above, tracked by figlet's own manifest -- continue? y
ok: figlet: removed 2 of 2 manifest file(s).
[e]
 
[h2]see also[e]
 
[see name="reference/commands/files"]files[e], [see name="reference/commands/remove"]remove[e], [see name="reference/commands/clean"]clean[e], [see name="reference/commands/owns"]owns[e].