On 11/29/22 10:44, Dominique Leuenberger / DimStar wrote:
There is at least tripple the OBS resource consumption to build a package three times, instead of once.
There is at least tripped the openQA resource consumption to test three flavors instead of one.
The openQA test results are, in most cases, expected to be the same. Yet, somebody has to do the work to review the failures and tag them with the corresponding bug reports (most frequently probably copying them from the STandard Tumbleweed port). Doing this on 2 extra ports is definitively more work than not doing this. And the occasional (albeit rare) case of something really being specific to x86-64-v1 (and i586, as announced, this won't be part of Tumbleweed anymore) will need to be analyzed and fixed.
I hope this is not news for you - but nothing comes for free in this world. At least some heartbeets and sweat-pearls need to be invested in everything. The expectation that 'somebody is doing it' only works until there is nobody else volunteering todo the work.
I think one of the barriers is that openSUSE isn't really a porter-friendly distribution. For example, I have been trying for ages to find proper documentation on how to bootstrap openSUSE on a new architecture, but nothing seems to exist. There cross-compilation capabilities in openSUSE are also rather limited as compared to Debian, for example. If openSUSE was accessible in this regard as Debian, I wouldn't mind maintaining additional architectures there. In Debian, I'm currently maintaining 9 architectures for Debian Ports without much hassle. Adrian