I’m not clear why 2,3 and 4 are needed.
I certaintly can see why a copr might be needed, but for the rest its unclear.
2 would be needed because 32-bit wine and 32-bit games are still prevalent, and shipping all of the dependencies of true 32-bit wine is untenable for a project like Bazzite. Wow64 fixes that problem, but it’s still experimental.
3 is needed because of what I mentioned at the end of problem 2 - If we need a custom version of Proton to work around this, every end user of ours would need to manually install that version of Proton, keep it up to date, and individually set every game in their library to use it.
4 occurs because OBS VKCapture depends on 32-bit Mesa and is itself a 32-bit plugin for capturing 32-bit games, which while uncommon now, make up the majority of games in the Steam library.
I apologize for any theatrics, they’re not intentional or an attempt to apply pressure, rather I wanted to make it clear that this change as-written makes it impossible for us to guarantee a stable and functional gaming experience as we have been.
At the same time, i find @kylegospo 's comment disingenuous, because while not great, they can revert to how they used to run Steam, as an exported app from a Distrobox container. It wasn’t perfect, but it worked for a long time. Also, making a copr repo of these packages wouldnt be so bad, there is already a copr repo for many custom packages in the project.
@yulian
There’s some revisionist history going on here. While we did experiment early on with containerizing Steam, this was only done on Desktop images. We dropped it completely because it has numerous unfixable problems that make it a bad experience. At no point did this power the gamemode session images of Bazzite because it can’t, for the same reasons the Flatpak can’t, and the gamemode session images are 2/3rd of our users.