docs/reference/commands/revdep.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 revdep[e]
 
[h2]synopsis[e]
 
[code]
mp revdep <pkg>
[e]
 
[h2]description[e]
 
lists every installed package genuinely linking against the given one, read from mp's own recorded link dependencies (linkdeps.db) -- not declared [code]pkg_deps[e] (that's [see name="reference/commands/why"]why[e]). the two can differ: something can declare a dep it never links (a build tool used only at compile time) or link something it never explicitly declared as a dep.
 
worth checking before [see name="reference/commands/remove"]mp remove[e]-ing a shared library or similar -- [code]remove[e] itself doesn't consult this.
 
a package routed into a sysroot has its own, separate linkdeps.db; revdep swaps into that scope for the lookup so it checks the right one. a bare name for a statically slotted package resolves to its one installed slot, same as [see name="reference/commands/why"]why[e]/[see name="reference/commands/tree"]tree[e]/[see name="reference/commands/remove"]remove[e].
 
[h2]examples[e]
 
[code]
mp revdep libpng
figlet
mp revdep zlib
warn: nothing currently links against zlib.
[e]
 
[h2]see also[e]
 
[see name="reference/commands/why"]why[e], [see name="reference/commands/remove"]remove[e], [see name="reference/commands/files"]files[e].