Am Sun, 3 Dec 2017 09:09:37 -0500 schrieb "Spackman, Chris" <ch...@osugisakae.com>:
> emerge --resume --skipfirst `emerge --resume --skipfirst` is necessary if you don't use --keep-going y, a package fails to build and you want to manually resume the actual emerge. Not using --skipfirst wouldn't make much sense, because the broken package will fail to build again anyway. Maybe Dales suggestion would work here. In this case you shouldn't use --skipfirst after fixing the reasons why the package failed to build. If you run `emerge -e @world` e.g. and get a power failure then you shouldn't use --skipfirst because then you want to build the package which was currently built during the power failure again. If you want to do have emerge doing a --resume --skipfirst automatically then you should use --keep-going y in the original emerge command like `emerge -e --keep-going y @world` or `emerge -uDN --keep-going y @world`. Heiko
