Re: [gentoo-user] emerge --resume question

[Jason Stubbs]

On Monday 03 April 2006 20:39, Peter Ruskin wrote:
> On Monday 03 April 2006 12:06, 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?
>
> I'm just experiencing the same thing - with over 800 ebuilds this is
> an important question.  I'm noting the problem ebuilds in a log
> file manually, so I can see to them when it's all over.

This is resilient to the single merge between resumes case in 2.1_pre.
For 2.0, you can manually back up and restore /var/cache/edp/mtimedb.

--
Jason Stubbs
-- 
gentoo-user@g.o mailing list