docs/reference/commands/conflicts.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 conflicts[e]
 
[h2]synopsis[e]
 
[code]
mp conflicts <pkg[:slot]>                  # list
mp conflicts <pkg[:slot]> +token -token ... # toggle
[e]
 
[h2]description[e]
 
with no +/-token arguments, lists what's currently effective for this port: its own declared [code]pkg_conflicts[e] plus any persisted [code]CONFLICTS=[e] override already in effect.
 
with [code]+token[e]/[code]-token[e] arguments, toggles relative to the current effective set, then persists the result under the port's bare name. a token carries [code]pkg_conflicts[e]' own [code]![e]/[code]!![e] soft/hard markers as part of its literal spelling -- lifting a declared soft conflict needs the same leading [code]![e] the declaration used ([code]-!somepkg[e], not [code]-somepkg[e]), and [code]+!!otherpkg[e] adds a hard blocker the port itself never declared at all.
 
[h2]examples[e]
 
[code]
mp conflicts figlet
!oldfiglet
mp conflicts figlet -!oldfiglet +!!reallyold
ok: figlet CONFLICTS set to: !!reallyold.
[e]
 
[h2]see also[e]
 
[see name="reference/commands/use"]use[e] (identical +/- toggle convention), [see name="reference/commands/info"]info[e].