Simplifying snapcraft.yaml

[Kyuyrii]

I simplified the snapcraft.yaml file; it was absurdly large and complex before.

Now it's easier to build the Snap version, as it will use the .deb version as a base.

I was able to build, install, log into my account, download a game, and launch it.

---

Use the following Checklist if you have changed something on the Backend or Frontend:

• Tested the feature and it's working on a current and clean install.
• Tested the main App features and they are still working on a current and clean install. (Login, Install, Play, Uninstall, Move games, etc.)
• Created / Updated Tests (If necessary)
• Created / Updated documentation (If necessary)

[Kyuyrii]

This is just proof that it's working.

At the beginning of the video, all the existing plugs and those that are connected are shown; the steam-support plug is essential for the Proton/UMU-launcher to function.

2025-12-23.04-52-07.mp4

[Kyuyrii]

Testing the mangohud

2025-12-24.13-19-39.mp4

[Kyuyrii]

The feature to create game shortcuts in the application menu is working.

2025-12-24.17-02-33.mp4

[CommandMC]

I have no clue what half of the changes in this file do, but as I've mentioned elsewhere, I'm willing to try a Snap build again as long as it doesn't cause any major issues

[CommandMC]

Can we load this version number from package.json? Ideally we'd just have one version number to bump each update

[a5ehren]

definitely possible, but takes some script wrangling.

The other option would be to take another crack at using electron-build's native snap target, which brings in the version automatically.

[CommandMC]

Why is $SNAP/usr/games added to PATH here?

[Kyuyrii]

In the kde-neon-6 extension, this is set via desktop-launch, but this isn't done in the gnome extension, so I had to set it in snapcraft.yaml.

[flavioislima]

@Kyuyrii I will try to build this and publish it on snap store, would it work? Or this is just for the manual installation? for the manual installation we can distribute the .snap using the elctron builder we already have, would just need to adjust the release command: https://www.electron.build/snap

[Kyuyrii]

@Kyuyrii I will try to build this and publish it on snap store, would it work? Or this is just for the manual installation? for the manual installation we can distribute the .snap using the elctron builder we already have, would just need to adjust the release command: https://www.electron.build/snap

To publish to the Snap Store, you need to request automatic connection of the steam-support plug; it is extremely important for UMU to function.

[Kyuyrii]

Generally, plugs added to Snap apps that aren't connecting automatically don't prevent them from being published, but there are some exceptions for security reasons.

[flavioislima]

@Kyuyrii I will try to build this and publish it on snap store, would it work? Or this is just for the manual installation? for the manual installation we can distribute the .snap using the elctron builder we already have, would just need to adjust the release command: https://www.electron.build/snap

To publish to the Snap Store, you need to request automatic connection of the steam-support plug; it is extremely important for UMU to function.

I see, I think we had a thread somewhere at some point but I think I would need to start a new one.
This is the error log for the build on snapcraft:
https://launchpadlibrarian.net/841753634/buildlog_snap_ubuntu_noble_amd64_018236f3314e147646868ec87cc16db2_BUILDING.txt.gz

[Kyuyrii]

I see, I think we had a thread somewhere at some point but I think I would need to start a new one. This is the error log for the build on snapcraft: https://launchpadlibrarian.net/841753634/buildlog_snap_ubuntu_noble_amd64_018236f3314e147646868ec87cc16db2_BUILDING.txt.gz

The error was about not finding the desktop-launch-heroic file. Locally, this error didn't occur here, but I modified the command-chain source to see if it fixes the problem.