It can be useful to have portage generate a list of URIs that will be downloaded for an operation since it allows machines with slow/metered/no internet connections to create a list that can be taken to a better connected machine for actually doing the download. This can already be done using: # emerge --pretend --fetchonly foo but the several potential URIs for each file on the same line. The attached tiny patch tp portage.py changes this to one URI per line, which makes the output suitable for feeding straight into wget, eg: # emerge --pretend --fetchonly foo > fetchlist # wget --no-clobber --input-file=fetchlist (--no-clobber stops wget grabbing the file multiple times, once from each of the mirrors) There is some non-URI cruft in the output, but wget just ignores it. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 7847 [details, diff] Tiny patch to portage.py, changes a " " to a "\n"
No. Use a quick sed if you feel this necessary. Space seperated has other functions.
