Re: [gentoo-portage-dev] Re: The merge of emerde with emerge

[Ed Grimm <paranoid@gentoo.evolution.tgape.org>]

On Fri, 3 Dec 2004, Dennis Bliefernicht wrote:

> Colin Kingsley wrote:
>>>What about emerge --resume --skipfirst in this case? Does quite the
>>>thing you want to do here :)
>>
>> No it doesn't.
>>
>> --resume restarts an aborted or failed merge, but it starts it at the
>> _beginning_ of the last package being worked on. All compilation of
>> that package must be repeated.
>>
>> --skipfirst just skips the first package to be merged during a
>> --resume. It is only there so that when one package has compile
>> problems you can ignore it instead of actualy fixing them.
>
> The intention was "If you want to skip the current merging", Ctrl-C
> and emerge --resume --skipfirst does exactly that. Compilation of the
> package in progress is irrelevant as it's the package that should be
> skipped :)

I'm curious...  I have 50 packages I want to install; miraculously,
there are no unsatisfied dependencies (not that surprising if I've done
--onlydeps).  The second package decides to blow up in some spectacular,
non-aborting fashion - let's say it starts apparently re-compiling itself
repeatedly.  I abort, I restart with --resume --skipfirst.

Now, package 15 decides that it wants to run a test, which claims it's
going to take 15 hours to complete.  I abort, I restart with --resume
--skipfirst.  What package starts compiling?  2, 15, or 16?

Ed

--
gentoo-portage-dev@gentoo.org mailing list