97bb4d8 Galaxy: Select build by build id
Make it possible to select by build id
Tries to find build with build id first
If no build is found with specified build id then try to use it as build index
If build id or index is not valid then default to build index 0

d83ba7f Add option to select network interface for operations
Adds option --interface

8dce7a3 Change --wishlist into --list option
Remove --wishlist
Add --list wishlist

--download-file was made to download files using their id
It was made so lgogdownloader could be used with the old gogdownloader:// links or as a download agent for other tools that want to download specific installers/extras
for example using as download agent for makepkg on Arch Linux

Example: downloading soundtrack for Tyrian 2000
Get the file id you want from --list details output $ lgogdownloader --download-file tyrian_2000/9543
or
$ lgogdownloader --download-file 1207658901/9543


There isn't an option to do version comparison when using Mojosetup files as Galaxy depot for Linux installers at the moment.
The mojosetup hack is kinda dumb currently and doesn't try to check version numbers in any way and instead just always updates the installed files if there are differences found in the installer.
Not really sure how much work it is going to be to add all the logic needed for that since I haven't looked at that code in a while.
I'll have to look into it some more.

I see. The way to hack around that is to use gameinfo or game/goggame-<id>.info files that exists in Linux installers and extract versions / build information from there. That's what I wanted to do in my script at least, but to do that it needs an ability to download only one specific file from inside the installer.

UPDATE:

Actually using --list details shows the version! Thanks for the tip:

lgogdownloader --list details --platform l --game drova
...
gamename: drova_forsaken_kin
product id: 1254250206
title: Drova - Forsaken Kin
icon: https://images-1.gog-statics.com/5c7c8507bde7278261729ccb1d187a75c330eeebf34f0514e26266541522f11a.png
installers:
id: en3installer0
name: Drova - Forsaken Kin
path: /drova_forsaken_kin/drova_forsaken_kin_1_0_6_77800.sh
size: 1306525696
updated: False
language: English
version: 1.0.6

So I can detect that version has changed using my own script since I can extract the version from those files in the alredy installed game. That would make triggering the update more sensible.

UDPATE 2:

Hm, is there some way to get game name using game id? Because --list details works with names, but my script works with game ids.

For now I can hardcode it.

UDPDATE 3:

Actually, linux updating with "pseudo-Galaxy" using the installers isn't so dumb - if files are up to date, it's not downloading them.

I noticed an interesting pattern in updating behavior.

If file is added to a blacklist, then lgogdownloader treats it as an orphan and deletes it (when running with deleting orphans). The only way to prevent that is to add it also to the ignorelist at the same time.

This helps the case of locally modified file that you want to be left untouched.

If the file is only is the ignorelist though (and not in blacklist), it will be overwritten by the file from the server if they differ. That's a bit counter-intuitive. May be the locally modifed file that's not really an orphan should not be replaced if it's in the ignorelist?

This should have been fixed by
cc44c35 Don't consider blacklisted files to be orphaned
b37dafb Galaxy: Don't consider blacklisted files to be orphaned

The idea behind ignorelist was initially to just work with orphan check so I could have it ignore any additional files (mostly mods) I store with the game files but it indeed works a bit counter-intuitive.
And with the the above changes to how blacklist works it kind of becomes irrelevant since one can just add files to be ignored into blacklist and have it work the same way as if they are ignorelisted.
I'll have to think about what to do about ignorelist. Maybe I'll even remove the option since blacklist can be used for the same purpose.

Ah, I see thanks - good to know! I have the version from the Debian repo which didn't get that change yet since it's not in the tagged version. I can apply that patch manually for now.

Yeah, I'm using ignorelist for mods now too. If one option will handle both - I guess it simplifies things.