Posted July 09, 2020
ikrananka: As far as I know, the original gogrepo.py script was developed in the early days of Galaxy before GOG really started messing things up with both Galaxy and Standalone installers. As such, the original gogrepo.py didn't include any code for selecting the installer type. So, running it today I have no idea which one it would default to.
I've now done some testing the good old fashioned way ... sort of. I used browser links to download the following games, then used TeraCopy to compare them with the versions I got with gogrepo.py, and they proved to be identical. So I suspect that answers the question, though admittedly I only did a small sample group.
Memoranda - setup_memoranda_gog-4_(11000).exe
Time Commando - setup_time_commando_1.0_(28045).exe
Cosmic Star Heroine - setup_cosmic_star_heroine_1.19_(22973).exe
Deep Diving Simulator -
setup_deep_diving_simulator_1.20_(32506).exe
setup_deep_diving_simulator_1.20_(32506)-1.bin
So that confirms what I thought was the most likely scenario, and I imagine any Galaxy arrangement in the manifest would be new and different to what the original version of 'gogrepo.py' was obtaining, which because it still works, means nothing has changed ... as you would expect. That makes the most logical sense anyway.
I'm not entirely sure why you would want to grab Galaxy downloads via 'gogrepo.py' anyway. I guess it is great that they are supported by Kalanyr's version of 'gogrepo.py', but why do it? What benefit do you gain?