ssokolow
commented
2 years ago If that docker run ... command is acceptable, maybe I should experiment with making a Flatpak build definition for it.
-
While Flatpak isn't specifically intended for non-GUI applications,
flatpak run com.github.Sude-.lgogdownloader <args>is less awkward than thatdocker runcommand and I have a proof of concept for auto-generating/updating wrapper scripts from theflatpak info -moutput that allow me to run Flatpak'd stuff likempvjust the same as if I were running the APT-provided versions.(My proof of concept uses the
command=mpvline output byflatpak info -m io.mpv.Mpvto determine what the wrapper should be called and punts on resolving naming conflicts since it's just a PoC. Not perfect, as in cases likecommand=scummvm_wrapperorcommand=PPSSPPSDLorcommand=com.github.tchx84.Flatseal, but pretty damn close for something with no special-casing or upstream buy-in.) - It'd work on any distro thanks to
flatpak-builderand the Flatpak runtimes being equivalent to the Docker build process. -
It could be published to Flathub so people who may be on LTS distros can still get automatic updates without having to do their own builds from source.
(Flatpak also has integration plugins for updater GUIs like GNOME Software and KDE Discover, making it as comfortable to keep up to date as APT/RPM/etc.)
- If distributed with default
filesystem=hostpermissions (unsandboxed, except for the bits overlayed by Flatpak's equivalent to the Steam Runtime and the bits explicitly blacklisted), it'd be easy for end users to use Flatseal or theflatpak overrideCLI command to narrow the sandbox to just the folders where they maintain their GOG collections. -
If you wanted to explicitly support sandboxed operation, I think some of the game engine reimplementations on Flathub use a launcher script which invokes
zenityon first run to request a "Select the directory where your game assets are" dialog which will be permanently granted into the sandbox.(Thus removing the need for
filesystem=host... but please don't yet. I'm on Kubuntu 20.04 LTS, directory picker support was added to the spec late in the game, Kubuntu 20.04 LTS is a bit too old for the KDE portal host to have directory picker support, and the Flatpak PPA only provides an updated version of the GTK/GNOME portal host.)
@Sude- If I were to produce a working Flatpak manifest (build definition), would you be willing to at least consider having it be an official thing? If published to Flathub, they'll provide the build service for the manifest, similar to how Jekyll is integrated into GitHub Pages.
(I haven't tried it, since I like to keep my downloading and managment of installed games firmly separated, but Minigalaxy is already on Flathub.)
shakeyourbunny
acheronfail
abhiaagarwal
This isn't exactly an issue, but I'm just letting you know that I created a docker image for
lgogdownloadersince I wanted to use it on a machine which couldn't easily install all the build dependencies, etc.It might come in handy for others too, so posting it here: https://github.com/acheronfail/lgogdownloader-docker
See the README for more information, but its usage is exactly like using the command (you just have to remember to map the config and data directories, etc).
Other notes:
lgogdownloaderstores its config files - from what I could see in the help text there's no option to control this