portage-ng --merge
>>> Emerging : portage://net-analyzer/arping-9999:run?{[]}
These are the packages that would be merged, in order:
Calculating dependencies... done!
└─step 1─┤ keyword portage://net-analyzer/arping-9999 (**)
└─step 2─┤ download portage://net-analyzer/arping-9999
│ └─ live ─┤ live git repository
│ download portage://net-libs/libnet-1.3-r1
│ └─ file ─┤ 581.54 Kb libnet-1.3.tar.gz
└─step 3─┤ install portage://net-libs/libnet-1.3-r1
│ └─ conf ─┤ USE = "-man -static-libs -test"
│ │ SLOT = "1.1"
└─step 4─┤ run portage://net-libs/libnet-1.3-r1
└─step 5─┤ install portage://net-analyzer/arping-9999 (**)
│ └─ conf ─┤ USE = "seccomp filecaps -test"
│ │ SLOT = "2"
└─step 6─┤ run portage://net-analyzer/arping-9999
Total: 7 actions (1 keyword, 2 downloads, 2 installs, 2 runs), grouped into 6 steps.
581.54 Kb to be downloaded.
>>> Assumptions taken during proving & planning:
Keyword acceptance (1 package):
Add to /etc/portage/package.accept_keywords:
net-analyzer/arping **
>>> Blockers added during proving & planning:
[blocks B] !net-misc/iputils (soft blocker, phase: install, required by: portage://net-analyzer/arping-9999)
[blocks B] !net-misc/iputils (soft blocker, phase: run, required by: portage://net-analyzer/arping-9999)