It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
.Keys: If you can bash script, to write a little script that extracts and then compress your Linux GOG ports using 7z, PeaZip, or anything really, is easy and can save you a lot of space. :)
An example of a shell implementation can be found in ./play.it codebase:
https://forge.dotslashplay.it/play.it/scripts/-/blob/2.24.0/src/30_archives/30_type_mojosetup.sh#L25
The makeself_* functions this relies on are set here:
https://forge.dotslashplay.it/play.it/scripts/-/blob/2.24.0/src/30_archives/30_type_makeself.sh#L69
Post edited July 21, 2023 by vv221
I am not sure if this is a good idea.

Yes, it would be more userfriendly in many cases, but if you want to edit files from the game (like config-files etc.) AppImage makes it more hard. Some games even write their save-files into the games directory, which wouldn't be possible anymore.

And what about games having the Mod-Directoy in the games Directory?!
avatar
.Keys: I do not know for certain how they do their .sh setup installers, only that they use MojoSetup and that the compression is not that good. But I've come across a Python script (Therefore, easily usable on Windows too) a while ago on GitHub that allows us to extract them and see its contents without "installing/extracting" the game as intended:
What I'd like to know is if the installers would be better if they were recomplied to at the very least, the 2020 edition of MojoSetup.
avatar
g2222: Anyone here who knows what those *.sh files are that GOG currently uses for Linux? I mean, I know that they are bash shell scripts with a binary appendage.
But what archive format is this? Can I somehow preview the data contents in Windows? 7-zip and WinRar don't seem to know how to handle this.
If you have Windows Subsystem for Linux set up in your Windows machine, while in the folder with the installer through the terminal, you can use the command unzip gog-setup-file-name-goes-here.sh to extract a given installer, and either unzip -Z1 gog-setup-file-name-goes-here.sh >> files-list.txt or zipinfo -1 gog-setup-file-name-goes-here.sh >> files-list.txt to list files in the installer, with the latter 2 commands creating a "files-list.txt" file which will have the files from inside the installer listed. Using the command through a Linux virtual machine should also be possible.
Post edited July 21, 2023 by _Auster_
avatar
g2222: Anyone here who knows what those *.sh files are that GOG currently uses for Linux? I mean, I know that they are bash shell scripts with a binary appendage.
But what archive format is this? Can I somehow preview the data contents in Windows? 7-zip and WinRar don't seem to know how to handle this.
avatar
_Auster_: If you have Windows Subsystem for Linux set up in your Windows machine, while in the folder with the installer through the terminal, you can use the command unzip gog-setup-file-name-goes-here.sh to extract a given installer, and either unzip -Z1 gog-setup-file-name-goes-here.sh >> files-list.txt or zipinfo -1 gog-setup-file-name-goes-here.sh >> files-list.txt to list files in the installer, with the latter 2 commands creating a "files-list.txt" file which will have the files from inside the installer listed. Using the command through a Linux virtual machine should also be possible.
you should be able to extract them with 7z on the command line by doing 7z x -tzip setup.sh
Lets put it this way, I have made myself and used for a few months now appimages from my GOG collection without problems.
I now have over 200 appimages of all games i own. No problems whatsoever
avatar
Timboli: (...)
avatar
.Keys: I do not know for certain how they do their .sh setup installers, only that they use MojoSetup and that the compression is not that good. But I've come across a Python script (Therefore, easily usable on Windows too) a while ago on GitHub that allows us to extract them and see its contents without "installing/extracting" the game as intended:

https://github.com/Yepoleb/gogextract

And an explanation on how GOG Linux setups work, by the script creator:

https://yepoleb.github.io/blog/2016/10/09/how-the-gog-linux-installers-work/

It worked with everything I tested it in. (Practically all the Linux ports on GOG of games I own.)

If you can bash script, to write a little script that extracts and then compress your Linux GOG ports using 7z, PeaZip, or anything really, is easy and can save you a lot of space. :)
Thanks for the info.
I'm not sure I was aware of it, though I may have been and dismissed it because there is no List or Test option.
7-Zip works well enough for me, with the correct command-line usage.
In any case, I am more concerned about the MD5 value and size check.
avatar
Bladeforce: Lets put it this way, I have made myself and used for a few months now appimages from my GOG collection without problems.
I now have over 200 appimages of all games i own. No problems whatsoever
How you did it? Do you have any guides on it?
Seems like something interesting to learn to do.
It may come in handy.

avatar
Timboli: Thanks for the info.
I'm not sure I was aware of it, though I may have been and dismissed it because there is no List or Test option.
7-Zip works well enough for me, with the correct command-line usage.
In any case, I am more concerned about the MD5 value and size check.
You're welcome!
What command line you use for 7z?
This is what I use:

7z a -t7z -m0=lzma2 -mx=9 -mfb=256 -md=512m -mmt=2 -mmc=10000 [archive name.7z] [file or folder to compress]

But I do not have so much knowledge in compression.
Still, this worked well with good results as compressible files have -50% to -70%, and in some rare cases, -90% file size compression with those commands.
avatar
.Keys: What command line you use for 7z?
This is what I use:

7z a -t7z -m0=lzma2 -mx=9 -mfb=256 -md=512m -mmt=2 -mmc=10000 [archive name.7z] [file or folder to compress]

But I do not have so much knowledge in compression.
Still, this worked well with good results as compressible files have -50% to -70%, and in some rare cases, -90% file size compression with those commands.
It seems we have a misunderstanding, I was talking about checking SH files, not compressing.

These are the two commands I use.

(TESTING) 7z.exe t -tzip "$path"

(LISTING) 7z.exe l -tzip "$path"
avatar
.Keys: What command line you use for 7z?
This is what I use:

7z a -t7z -m0=lzma2 -mx=9 -mfb=256 -md=512m -mmt=2 -mmc=10000 [archive name.7z] [file or folder to compress]

But I do not have so much knowledge in compression.
Still, this worked well with good results as compressible files have -50% to -70%, and in some rare cases, -90% file size compression with those commands.
avatar
Timboli: It seems we have a misunderstanding, I was talking about checking SH files, not compressing.

These are the two commands I use.

(TESTING) 7z.exe t -tzip "$path"

(LISTING) 7z.exe l -tzip "$path"
Oh, my bad then. :)
Thank you for explaining.