Alan McKinnon wrote: > On 12/11/2015 10:48, Jörg Schaible wrote: >> Alan McKinnon wrote: >> >>> On 12/11/2015 10:29, Jörg Schaible wrote: >>>> Alan McKinnon wrote:
[snip] >>>> 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. > > I've never noticed that. For me --skip-first has always skipped the > correct first package (the one that previously failed). That's what I always did originally also, until my build suddenly broke at the same package again and I had to notice that it skipped a completely different. > As long as a known build failure is not in the --resume list, I don't > care what the build order is because it is irrelevant. The only time it > becomes relevant is when an ebuild has a bug such as a missing dep. But > that's a bug in the ebuild and is fixed there. Well, normally I don't care about the sequence either, except when skipping the first ;-) Cheers, Jörg
