| 1 |
Matthias Langer wrote: |
| 2 |
> 2.) emerge -e world on a system with lot of packages will most likley |
| 3 |
> fail somewhere during the process for various reasons. Fixig the problem |
| 4 |
> (for example by unmerging the package which causes it) and restarting |
| 5 |
> the process is not an option, as this may cost you lot's of time. In my |
| 6 |
> case, emerge -e world stopped 3 times. To continiue without starting it |
| 7 |
> all again, i did |
| 8 |
> |
| 9 |
> # emerge --resume -p > package.list |
| 10 |
> |
| 11 |
> and then edited this file with vi so that |
| 12 |
> |
| 13 |
> # emerge --oneshot --nodeps `cat package.list` |
| 14 |
> |
| 15 |
> continued the process, leafing out the brocken package. The be honest, i |
| 16 |
> expected to find some freaky sed command to accomplish what i did with |
| 17 |
> vi (thanks to the makro recorder) in the gcc-3.4 migration guide. |
| 18 |
|
| 19 |
Why not just use --resume --skipfirst? |
| 20 |
|
| 21 |
Marius |
| 22 |
-- |
| 23 |
gentoo-dev@g.o mailing list |
Archives