On Tue, 2022-12-06 at 10:40 +0100, Stephan Kulow wrote:
On 06.12.22 10:23, Dominique Leuenberger / DimStar wrote:
On Tue, 2022-12-06 at 10:16 +0100, Stephan Kulow wrote:
On 06.12.22 09:40, Michael Ströder wrote:
"Someone" has decided to go with x86_64-v2, forcing others to either do more work or buy new hardware. And now you blame the "others" to expect "somebody else" to do the work for them. I'm also wondering why SUSE thinks anybody in the community would appreciate this move. Overall it's very discouraging.
I for one still need to hear *any* argument to duplicate x86_64. The only one I heard was "factory first" - but how do the compiler flags matter between code streams that will soon enough diverge in compiler versions wasn't really explained at all.
so, your proposed solution would be to just kick i586 to the curbs (ports) and leave the x86_64 port at baseline? Or go v3? or not build x86_64 for baseline and go v2 in TW? or ignore everything and let it all just the way it is? I would indeed prefer if we dropped i586 before we touched x86_64. And having v2/v3 biarch repo sounds appealing to me - but obviously is a little harder to get.
Greetings, Stephan
i586 (except -32bit packages) are scheduled to go out to the ports as well (if somebody cares to look after it) Having TW itself as v2/v3/v4 multiarch would be really interesting indeed, and I do hope that for the time when we want to start discussing to raise to a next level post v2, the infrastructure (build/QA and also zypper and rpm) can be thought about this. in OBS we could add multiple repos (v2/v3) and have them built (v3 a bit slower, due to a smaller hw pool for it in OBS), but then if they end up in repo, zypper has no clue which one to pick. And for this, I think RPM should also gain some support as it should not just call the arch x86_64 in this case, but differentiate between the subsets we would build for. That's certainly something to look at *in the nearer future*. if we only move i586 to the Legacy port, then I really doubt we will have anybody looking after that port at all, even though we heard people wanting i586; so far the only volunteer to look after the legacy port is still only Jiri; so in t Cheers, Dominique