Yo! I’m trying to create the umu-support interface. It’s designed to make the UMU launcher work within Snap, but not just the UMU launcher alone; it’s intended for use with game launchers that use UMU/Proton/Wine.
I tested it with Heroic and Zordeer, and both were able to run games, but I need many more people testing these launchers with umu-support connected to know how far this interface can go.
The pull request that needs to be merged to add umu-support is this one:
This is great!
But why call it ‘umu-support‘ instead of some name like ‘game-launcher-support‘?
The name is umu-support because it was designed with UMU and launchers that use UMU in mind.
Most of the permissions that umu-support offers are apparently not necessary for a launcher that uses Wine, Proton without UMU, and/or that runs native Linux games.
I made Snap versions of Minigalaxy and gogdl-cli to test them. Minigalaxy runs native games, and when there isn’t a native version, it uses Wine. gogdl-cli runs games using Proton; I managed to run Metro 2033 Redux on both, without needing the umu-support interface.
A name like “game-launcher-support” can be confusing, as it might imply that the interface is necessary for any type of game launcher to function.
Thx for your explanation.
I’d also call it rather something like pressure-vessel-support, but in the end discussions around the naming are moot, an architect will have to review the PR and approve it before it can get merged anyway and they will request name changes if it does not fit the current scheme or is to esoteric (I doubt many people know what “umu” is at all so something more descriptive would be good)
