portage-ng --fetchonly
>>> Emerging : portage://media-libs/libsvgtiny-9999:run?{[]}
These are the packages that would be merged, in order:
Calculating dependencies... done!
└─step 1─┤ keyword portage://media-libs/libsvgtiny-9999 (**)
│ keyword portage://net-libs/libdom-9999 (**)
│ useflag portage://net-libs/libdom-9999 (xml)
└─step 2─┤ download portage://dev-build/netsurf-buildsystem-1.10
│ └─ file ─┤ 38.30 Kb buildsystem-1.10.tar.gz
│ download portage://dev-libs/libparserutils-0.2.5
│ └─ file ─┤ 72.77 Kb libparserutils-0.2.5-src.tar.gz
│ download portage://dev-libs/libwapcaplet-0.4.3-r1
│ └─ file ─┤ 31.02 Kb libwapcaplet-0.4.3-src.tar.gz
│ download portage://media-libs/libsvgtiny-9999
│ └─ live ─┤ live git repository
│ download portage://net-libs/libdom-9999
│ └─ live ─┤ live git repository
│ download portage://net-libs/libhubbub-0.3.8
│ └─ file ─┤ 762.25 Kb libhubbub-0.3.8-src.tar.gz
Total: 9 actions (2 keywords, 1 useflag, 6 downloads), grouped into 2 steps.
904.35 Kb to be downloaded.
>>> Assumptions taken during proving & planning:
Keyword acceptance (2 packages):
Add to /etc/portage/package.accept_keywords:
media-libs/libsvgtiny **
net-libs/libdom **
USE flag change (1 package):
Add to /etc/portage/package.use:
net-libs/libdom xml