| 1 |
Neil Bothwick wrote: |
| 2 |
|
| 3 |
> On Thu, 12 Nov 2015 09:48:48 +0100, Jörg Schaible wrote: |
| 4 |
> |
| 5 |
>>> > Hmmm. And how can you then ever use |
| 6 |
>> >> |
| 7 |
>> >> emerge --resume --skip-fist |
| 8 |
>> >> |
| 9 |
>> >> if not even the first build is deterministic? I skip the first |
| 10 |
>> >> package anyway only if the problematic package is the first one to |
| 11 |
>> >> build after resume, but if I cannot even rely on that? |
| 12 |
>> > |
| 13 |
>> > |
| 14 |
>> > Because it re-uses the previous build order, not re-generate a new |
| 15 |
>> > one. |
| 16 |
>> |
| 17 |
>> That's simply not true. Emerge resume calculates the order again and |
| 18 |
>> for me it starts often with a different package. |
| 19 |
> |
| 20 |
> Then use emerge --keep-going and portage will take care of skipping |
| 21 |
> failing merges for you. |
| 22 |
|
| 23 |
Ah, no, that's not an option. It breaks for a reason. Sometimes I can ignore |
| 24 |
that and look for it later and in this case I skip it, but normally I fix |
| 25 |
the problem first. However, you have to take care, which package you're |
| 26 |
actually skipping. Especially if the build order is different with resume. |
| 27 |
|
| 28 |
Cheers, |
| 29 |
Jörg |
Archives