| 1 |
Alan McKinnon wrote: |
| 2 |
|
| 3 |
> On 11/11/2015 21:35, Walter Dnes wrote: |
| 4 |
>> Ongoing installation. I looked at 2 instances of |
| 5 |
>> "emerge -pv x11-base/xorg-server" and the order was somewhat different. |
| 6 |
>> Here are a couple of outputs, just a few seconds apart. Is this a bug |
| 7 |
>> or a feature? See attachments. |
| 8 |
>> |
| 9 |
> |
| 10 |
> |
| 11 |
> Emerge order is not deterministic, especially with parallel builds. The |
| 12 |
> reason is that it does not need to be according to the dep graph - if |
| 13 |
> two packages are at the same level and do not depend on each other, then |
| 14 |
> the order they are built in does not affect the final result. |
| 15 |
> Practically all parallel processing works this way. |
| 16 |
> |
| 17 |
> What is deterministic, is that if you build the same set of packages |
| 18 |
> twice and even if portage does them in different order, the binaries |
| 19 |
> produced are functionally identical |
| 20 |
|
| 21 |
Hmmm. And how can you then ever use |
| 22 |
|
| 23 |
emerge --resume --skip-fist |
| 24 |
|
| 25 |
if not even the first build is deterministic? I skip the first package |
| 26 |
anyway only if the problematic package is the first one to build after |
| 27 |
resume, but if I cannot even rely on that? |
| 28 |
|
| 29 |
Cheers, |
| 30 |
Jörg |
Archives