Neil Bothwick wrote: > On Thu, 12 Nov 2015 09:48:48 +0100, Jörg Schaible wrote: > >>> > Hmmm. And how can you then ever use >> >> >> >> emerge --resume --skip-fist >> >> >> >> if not even the first build is deterministic? I skip the first >> >> package anyway only if the problematic package is the first one to >> >> build after resume, but if I cannot even rely on that? >> > >> > >> > Because it re-uses the previous build order, not re-generate a new >> > one. >> >> That's simply not true. Emerge resume calculates the order again and >> for me it starts often with a different package. > > Then use emerge --keep-going and portage will take care of skipping > failing merges for you.
Ah, no, that's not an option. It breaks for a reason. Sometimes I can ignore that and look for it later and in this case I skip it, but normally I fix the problem first. However, you have to take care, which package you're actually skipping. Especially if the build order is different with resume. Cheers, Jörg
