portage-ng --merge
>>> Emerging : portage://sys-libs/musl-1.2.6-r2:run?{[]}
These are the packages that would be merged, in order:
Calculating dependencies... done!
└─step 1─┤ unmask portage://sys-libs/musl-1.2.6-r2
│ keyword portage://sys-libs/musl-1.2.6-r2 (**)
└─step 2─┤ download portage://sys-libs/musl-1.2.6-r2
│ └─ file ─┤ 11.34 Kb getconf.c
│ │ 2.52 Kb iconv.c
│ │ 6.96 Kb musl-1.2.6-patches.tar.xz
│ │ 1.03 Mb musl-1.2.6.tar.gz
│ │ 11.38 Kb musl-getent-93a08815f8598db442d8b766b463d0150ed8e2ab.c
└─step 3─┤ install portage://sys-libs/musl-1.2.6-r2 (**)
│ └─ conf ─┤ USE = "crypt -headers-only -verify-sig"
└─step 4─┤ run portage://sys-libs/musl-1.2.6-r2
Total: 5 actions (1 unmask, 1 keyword, 1 download, 1 install, 1 run), grouped into 4 steps.
1.06 Mb to be downloaded.
>>> Assumptions taken during proving & planning:
Keyword acceptance (1 package):
Add to /etc/portage/package.accept_keywords:
sys-libs/musl **
Package unmask (1 package):
Add to /etc/portage/package.unmask:
=sys-libs/musl-1.2.6-r2
>>> Blockers added during proving & planning:
[blocks B] !sys-libs/libxcrypt (soft blocker, phase: run, required by: portage://sys-libs/musl-1.2.6-r2)