portage-ng --fetchonly
>>> Emerging : portage://sys-kernel/rumpkernel-9999:run?{[]}
These are the packages that would be merged, in order:
Calculating dependencies... done!
└─step 1─┤ unmask portage://dev-util/mig-1.8_p20260123
│ unmask portage://sys-kernel/gnumach-1.8_p20260630
│ unmask portage://sys-kernel/rumpkernel-9999
│ keyword portage://sys-kernel/rumpkernel-9999 (**)
└─step 2─┤ download portage://dev-util/mig-1.8_p20260123
│ └─ file ─┤ 61.96 Kb mig-1.8_p20260123.tar.xz
│ download portage://sys-kernel/gnumach-1.8_p20260630
│ └─ file ─┤ 2.41 Mb gnumach-1.8_p20260630.tar.xz
│ download portage://sys-kernel/rumpkernel-9999
│ └─ live ─┤ live git repository
│ download portage://x11-libs/libpciaccess-0.19
│ └─ file ─┤ 63.21 Kb libpciaccess-0.19.tar.xz
Total: 8 actions (3 unmasks, 1 keyword, 4 downloads), grouped into 2 steps.
2.53 Mb to be downloaded.
>>> Assumptions taken during proving & planning:
Keyword acceptance (1 package):
Add to /etc/portage/package.accept_keywords:
sys-kernel/rumpkernel **
Package unmask (3 packages):
Add to /etc/portage/package.unmask:
=dev-util/mig-1.8_p20260123
=sys-kernel/gnumach-1.8_p20260630
=sys-kernel/rumpkernel-9999