Peter Campion-Bye wrote: >Hi, >Trying to do an 'emerge -e world' I come up against the odd package that >doesn't build without some intervention. I know I can do 'emerge --resume >--skipfirst' and carry on, but sometimes the broken package could be built ok >with a little intervention, for example, my build breaks on pilot-link, which >can be simply fixed with 'FEATURES="-sandbox" emerge pilot-link'. Problem is, >I can't do a resume after this as the emerge list from the world build has >been blatted when I emerged pilot-link. So, is there any way I can preserve >the state of the world build, so that after building the breaking package I >can do a --resume --skipfirst and carry on with the world build? >Any other suggestions for workarounds? >thanks > >
I did this once. I renamed the emerge.log then did what needed doing and then put the back-up back to it's original name, erasing the little that was generated while fixing something. It may not work in every case though but it may be worth a try. Dale :-) :-) -- [email protected] mailing list
