Name: Games Nebula
Home page: https://github.com/yancharkin/games_nebula
Why: As of now there's no official Linux client for gog.com. This would make installing and managing GOG games on Linux a lot easier/convenient.
Open source: yes
Link to the latest release: https://github.com/yancharkin/games_nebula/releases/download/20171113/games_nebula_20171113.tar.gz
Source repository: https://github.com/yancharkin/games_nebula
Name: Games Nebula
I managed to put together a package.yml that builds for lgogdownloader, a dependency for games nebula. Figure I may as well finish the job and do Nebula as well. I'll be submitting the patches for lgogdownloader and a couple dependencies after making sure it works.
I have all dependencies packaged and tested, but I got a question regarding the actual software. All other distros just packaged the dependencies and told them to use the setup.sh from the git repo, so my question is how should solus handle this? Similar? (I would write a guide inside the helpcenter) or trying to package even games nebula package?
The maintainer has tagged releases and the setup.sh only extracts the files to the correct place, creates a launcher, downloads some dependencies and extract them too. So my suggestion would be to check if those dependencies could be packaged and then doing the steps in the script via packaging. It would be an easy task to just prep a launcher and the folder structure to package it, as far as i know it's normal procedure to do it this way. From my POV, the dependencies being downloaded in the script are the only problem here.
I have all dependencies ready but dunno how exactly to continue with the main software and as said the other distros did not package the main software as well (the setup.sh works perfectly I tested it) my concern is the setup.sh has 3 yes/no condition which you have to set, which I totally don't know how to handle this
https://github.com/yancharkin/games_nebula/blob/master/setup.sh <- how should I handle this? Should Solus only give the user the needed dependencies and they run the setup.sh by themself?
It doesn't look like there's anything in there we couldn't do ahead of time. Add the zip archives as sources and extract them to the related directories in /usr/share/games-nebula/. Create the .desktop file ahead of time (having it switch to /usr/share/games-nebula before the exec).