1 |
My mother has a computer which still accesses the internet via a dialup |
2 |
connection. When I do upgrades on her system, I typically grab a portage |
3 |
snapshot from my system, drive up to her house 12 miles away, install |
4 |
it, check to see which packages need upgrading, then somehow figure out |
5 |
(never exactly) which files she actually needs so I can get them, again, |
6 |
from my system, drive those files back up to her house and compile stuff |
7 |
hoping I didn't miss anything too sizable. |
8 |
|
9 |
Question: Is there a way that I can get Portage to run through the |
10 |
packages/ebuilds and, instead of downloading anything from the net, just |
11 |
have it show me which files were not in /usr/portage/distfiles which |
12 |
will be needed? |
13 |
|
14 |
So if I had 8 packages which needed upgrading, which would result in (an |
15 |
estimated) 6,382K of downloads, is there some way for me to have it go |
16 |
through each one of those all at once, similar to --fetchonly, and have |
17 |
it spit out a list of everything which it did not find on the local |
18 |
system? |
19 |
|
20 |
It seems to be simple enough and a useful feature on some level but I |
21 |
haven't found the answer. |
22 |
|
23 |
Thoughts? |
24 |
|
25 |
-Statux |