Matthias Langer wrote:
2.) emerge -e world on a system with lot of packages will most likley
fail somewhere during the process for various reasons. Fixig the problem
(for example by unmerging the package which causes it) and restarting
the process is not an option, as this may cost you lot's of time. In my
case, emerge -e world stopped 3 times. To continiue without starting it
all again, i did
# emerge --resume -p > package.list
and then edited this file with vi so that
# emerge --oneshot --nodeps `cat package.list`
continued the process, leafing out the brocken package. The be honest, i
expected to find some freaky sed command to accomplish what i did with
vi (thanks to the makro recorder) in the gcc-3.4 migration guide.
Why not just use --resume --skipfirst?
Marius
--
[email protected] mailing list
