Alex Schuster wrote:
> Iván Pérez Domínguez writes:
> 
>> After installing Gentoo in different machines several times, I wonder if
>> is there any way to tell emerge to keep installing as much as possible
>> even when something goes wrong.
> 
> Sure there is. Have a look at the emerge man page, there 's lots uf useful 
> information. portage also has a nice man page.

I just read both (and make.conf as well). Maybe I missed something, but
I think that suggestion has not been implemented so far.

> 
> 
>>  emerge stuff1 stuff2 stuff3
>>
>> emerge says "the following packages will be emerged" and so on.
>>
>> Alright. Then stuff1 fails to compile. I'd like emerge to continue
>> trying to install stuff2 and stuff3 when possible.
> 
> emerge --resume --skipfirst
> This resumes the last emerge, skipping the first package. Leave 
> the --skipfirst to try again.

This one I already knew.

> I like to use "FEATURES=keepwork 
> emerge --resume" to resume an interrupted emerge without restarting from 
> scratch, but this feature seems to be broken at the moment.
> 
>> I know I could write several emerges in different lines (something like
>> emerge stuff1; emerge stuff2; emerge stuff3), I just feel like this
>> feature should have an option of its own in emerge (i.e.
>> --keep-going-as-far-as-possible).
> 
> Maybe, but on the other hand it's a little bash one-liner.

I don't get your point here, sorry.

> 
>> This could be very handy when updating world or, in general, when the
>> emerge is going to take a lot of time and you decide to leave, expecting
>> everything to be merged when you come back.
> 
> This will emerge world and continue after every error, skipping that 
> package:
> emerge world -u || while ! emerge --resume --skipfirst; do :; done
> 
> 	Alex
> 

As I said before, the line above (emerge a; emerge b; emerge c;) could
work as well. The main point is that, in my opinion, that feature should
be included in emerge itself.

Your line has a problem: it won't skip the first package in your line,
it will skip only the first package to be emerged, which may be a
required dependency to build another package, propagating an error in
one compilation to later compilations. Even worse, some package could
get installed without one of its dependencies.

   Ivan.