On 01. 12. 22, 10:43, Michal Suchánek wrote:
On Thu, Dec 01, 2022 at 10:25:22AM +0100, Jiri Slaby wrote:
On 23. 11. 22, 16:22, Dominique Leuenberger / DimStar wrote:
* openSUSE Tumbleweed main repository: + will move to x86-64-v2 (like ALP will)
Thinking about this more. Given we are going to have :LegacyX86 (likely?), can we move TW to -v3 instead?
_That_ would very make sense and _measurable benefit_ for vast majority of current machines.
Yes, if we are going to have two builds v1 and v3 makes more sense.
This won't be aligned with the current ALP plan, though.
Yeah, but I don't care about ALP at all in the above. AIU the politics, Factory has to have more, but not less. Which is satisfied by the above.
ALP plans only one build, v3 as only the build was rejected on the basis it excludes way too much hardware, and there seems to be some political pressure to go with something other than the basseline.
Agreed, having a v3-only build is a no-go, ATM. So keep ALP at v2 (which is nonsense from technical POV, but OK).
I think that investing into the infrastructure to make it possible to build and install select packages with support for newer CPUs in one way or another is really the way to go. Then users can benefit from the hardware features they have without excluding users that don't have them from using the distribution.
Also with providing the packages for different CPUs in one way or another we would get at least some download statistics which could be used for some rough estimate about the prevalence of hardware with different features. At this point we have absolutely no data on that.
+1. We can even have v2 for TW from the beginning to test the Factory -> Factory:LegacyX86 repo switch on fewer machines. Collect the download data of v2. And do the switch to v3. And collect the data again. We would know how much is v2 of use and v3 too. thanks, -- js suse labs