portage-ng --merge
>>> Emerging : portage://sys-boot/milo-2.4.18:run?{[]}
These are the packages that would be merged, in order:
Calculating dependencies... done!
└─step 1─┤ license portage://sys-boot/milo-2.4.18
│ keyword portage://sys-boot/milo-2.4.18 (**)
└─step 2─┤ download portage://sys-boot/milo-2.4.18
│ └─ file ─┤ 51.23 Kb MILO-HOWTO
│ │ 18.50 Kb ldmilo-patched-20010430
│ │ 7.00 Kb linload.exe
│ │ 151.31 Kb linux-2.2.20-reiserfs-3.5.35.diff.bz2
│ │ 15.06 Mb linux-2.2.25.tar.bz2
│ │ 1.02 Mb milo-2.2-18.tar.bz2
│ download portage://sys-fs/mtools-4.0.49
│ └─ file ─┤ 387.70 Kb mtools-4.0.49.tar.lz
└─step 3─┤ install portage://sys-fs/mtools-4.0.49
│ └─ conf ─┤ USE = "-gui"
└─step 4─┤ run portage://sys-fs/mtools-4.0.49
└─step 5─┤ install portage://sys-boot/milo-2.4.18 (**)
└─step 6─┤ run portage://sys-boot/milo-2.4.18
Total: 8 actions (1 license, 1 keyword, 2 downloads, 2 installs, 2 runs), grouped into 6 steps.
16.69 Mb to be downloaded.
>>> Assumptions taken during proving & planning:
Keyword acceptance (1 package):
Add to /etc/portage/package.accept_keywords:
sys-boot/milo **
License acceptance (1 package):
Add to /etc/portage/package.license:
==sys-boot/milo-2.4.18 MILO