docs/reference/commands/tree.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 tree[e]
 
[h2]synopsis[e]
 
[code]
mp tree <pkg> ...
[e]
 
[h2]description[e]
 
prints a package's own dependency tree, as declared -- not what's actually installed, and not filtered by whether a dependency resolved at all. each line shows the raw dependency token, and, if resolving it produced a different name (a %tag resolving to its concrete provider, say), " (-> resolved-name)" alongside it. an unresolvable dependency still prints (as a leaf, since there's nothing to recurse into), it just shows no arrow.
 
recursion stops the first time a given resolved name is seen again (a diamond dependency, or a real cycle) -- printed once, not expanded a second time underneath itself.
 
this reads the SAME effective-deps expansion (USE-conditional [code]DEPS+[e]/[code]DEPS-[e], %tag resolution) that a real install would use right now, given current config -- not necessarily what was true when the package was actually installed.
 
[h2]examples[e]
 
[code]
mp tree figlet
- figlet
  - %libc (-> musl)
  - %shell (-> busybox)
[e]
 
[h2]see also[e]
 
[see name="reference/commands/why"]why[e], [see name="reference/commands/providers"]providers[e], [see name="reference/commands/info"]info[e] (effective deps for one package, without the recursion).