docs/reference/commands/hold.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 hold[e]
 
[h2]synopsis[e]
 
[code]
mp hold <pkg>
[e]
 
[h2]description[e]
 
blocks install/remove/reinstall/update against the given package, persistently -- written as [code]HOLD=yes[e] under the package's bare name in [code]WD/pkgconf.conf[e] (mp's own overlay, never hand-edited). [see name="reference/commands/update"]mp update world[e] treats a held package specially: skipped with a note rather than aborting the whole batch, which a real build failure elsewhere still does.
 
a per-package [code]HOLD_VERSION=<ver>[e] key (set by hand in mp.conf/pkgconf.conf, not by this command) is a narrower form of the same idea: reinstall refuses to proceed unless the currently-installed version matches exactly, without blocking install/remove entirely the way a plain HOLD does.
 
[h2]examples[e]
 
[code]
mp hold gcc
ok: gcc held (persisted in /usr/mp/pkgconf.conf).
mp update world      # skips gcc with a note instead of touching it
mp unhold gcc
[e]
 
[h2]see also[e]
 
[see name="reference/commands/unhold"]unhold[e], [see name="reference/commands/mask"]mask[e] (blocks auto-pick/explicit install instead, a different axis), [see name="reference/commands/info"]info[e] (shows current hold status/reason).