I have app info with 2 app versions for same application, one for x86 platform, another - for x86_64 platform.

BOINC is x64.

Now I changed x86_64 version to point on new app leaving x86 w/o changes.

And nothing changed. Looking into client_state I found that all already downloaded tasks are marked with x86 platform tag though it's alternative one, not primary one.

In app info app_version with x86_64 platform located below x86 one.

If I place x86_64 app_version before x86 one in app info - will BOINC mark fresh tasks as for x86_64 platform? Or x86 app_version entry should be completely removed to achieve that?

---

I answered on this question experimentally.
Yes, if section position will be swapped x86_64 platform begins to dominate. Hence, order of app_section does matter in app_info.

This leads to another question: should it be so? BOINC has main platform (x86_64 in my case) and alternative one (x86).
Would it be more correct not to relate on arder in app_info but on this define instead and download for x86 platform only if x64 not available?

Having both platforms mentioned in app_info is good for multiboot hosts. But each boot way will have different primary platform (as should be) and order of app_info section swill remain the same (and this could cause troubles).

So, looks like feature request here: to remove dependence from order of app_version sections in app_info and to rely on other config properties like preferred platform instead.

---

I answered on this question experimentally.
Yes, if section position will be swapped x86_64 platform begins to dominate. Hence, order of app_section does matter in app_info.

This leads to another question: should it be so? BOINC has main platform (x86_64 in my case) and alternative one (x86).
Would it be more correct not to relate on arder in app_info but on this define instead and download for x86 platform only if x64 not available?

Having both platforms mentioned in app_info is good for multiboot hosts. But each boot way will have different primary platform (as should be) and order of app_info section swill remain the same (and this could cause troubles).

So, looks like feature request here: to remove dependence from order of app_version sections in app_info and to rely on other config properties like preferred platform instead.

Could we refine that request, please?

By all means give highest priority to primary platform when alternative platforms are available.

But please retain order of appearance as a secondary discriminant after the platform has been selected. To remove this code feature would break useful functionality.

I'm not sure that this is useful functionality and not deceiving one cause XML usually look for tags, not for their order in my understanding... But I would not object if this part will be ignored. Just consider they case when both platform needs to be listed. That case should work properly, that's all.

---