automatically migrate to newer GE-Proton

[intrand]

Ideally, if a game is set to the latest GE-Proton version, and then a new version of GE-Proton is released, the tool should attempt to migrate those games to the newest version. However, if the game is using a version of GE-Proton before that, it's probably set that way for compatibility reasons and the tool shouldn't touch it.

Relies on functionality from #6 being implemented first.

[intrand]

Feedback from Reddit: make it optional to migrate from the "previously latest" to the "now latest" version because sometimes new GE-Proton releases can break games that used to work, even in a single update.

Edit: source

[intrand]

Feedback from Reddit: when someone is without Internet access for a long enough period of time that GloriousEggroll happens to release more than one newer version of GE-Proton, the tool wouldn't be able to distinguish between outdated (eligable for automatic migration) and purposely configured (avoid migrating) compatibility tool settings.

Edit: source

[intrand]

This feature requires more thought.

Perhaps we could track compatibility tool configuration ourselves, but keeping state in multiple places is prone to bugs/desync. We could duplicate what ProtonUp-Qt has with the ability to migrate games manually, but why not just use that tool then? :)

[krillme]

Perhaps the tool could not only download the latest version of GE-Proton, but also duplicate it and name the duplicate something like "Latest Version". That way when a game is set to use "Latest Version", every time the tool updates GE-Proton it overwrites "Latest Version" with the most recent version so users don't have to manually configure games to use the latest version every time there's an update. If a game is set to use "Latest Version", it will always be the latest version (as long as you've downloaded it)

[HelmicNewciv]

Couldn't this be handled with a symlink?

Download GE-Proton versions as normal and give them their version name. Create a GE-Proton Latest folder and .acf and what have you, and have that symlinked to whatever the latest version is. Any game that is set to use the latest version will then use whatever the symlink is currently pointing to, and then you can keep a configurable number of rollback versions to keep installed. Once that number is exceeded, delete the oldest versions, not counting those explicitly set as used by a game (so not using GE-Proton Latest). Obviously don't count versions in use by a game towards the rollback limit.

[krillme]

Yes, that sounds like a more efficient solution than duplicating the files, especially on hardware with limited storage such as the 64 GB Steam Deck.

[intrand]

Apologies for my silence here - life has been very busy. Having it install an optional "latest" symlink might be a useful feature. I can look at testing this at some point.

Thanks for the feedback!

Also, if you are reading this and know how to write Go code, please feel free to give it a shot and submit a pull request if it looks promising.

[intrand]

This doesn't seem worth trying to implement as it can break things and has too many edge cases compared to simply using protonup-qt to manage installed versions (it has a migration feature).