You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It occurred to me that we talked a lot about shipping updated fixes rapidly, but we didn't talk about how they would actually be applied. If the fixes are being created after folks update/install the related app then they will have to manually trigger the updates to be applied.
Alternatively, either automatically, manually, or manually confirmed, a sha1 of the app fixes directory file list (with dates should be good enough) could be written to cache when applied. On boot steamtricks could compare the data directory for all installed games against their related hashs to see if they've changed. Once steam is quiet (ie might as well wait if it starts updating in first min or two) the updates could be triggered by requesting steam to validate the game.
The validation seems like best approach since it would clear any already applied changes and allow for a full re-application so that there is no need to try and diff with previous applied fixes or some nonsense. The only issue with that approach is whether an app validation can be triggered easily from outside the Steam UI, either via steam URL commands or perhaps tweaking a manifest file as they seem to track app states.
If system updates are run while steamtricks is running (probably common) that could be either detected via checking either the package version or a file in the root of data dir that contains the same and comparing against cache. Alternatively, the package could trigger a steamtricks command on postrun, but that is probably problematic since it would be running as root.
The text was updated successfully, but these errors were encountered:
The one bit that needs deciding is how to trigger the watch loop to detect/look for changes. Have the rpm write to a /tmp or log file of some sort just to notify the loop and then check hashes from there? Setting up inotify or somesuch seems like overkill and a bad idea and rpm has no easy way to communicate with users running steamtricks unless systemd provides some sort of facility.
Another item to consider is triggering when steamtricks itself updates as it may contain new generalized code that fixes issues with a games, but it is unlikely that re-checking all installed games at once is desirable.
It occurred to me that we talked a lot about shipping updated fixes rapidly, but we didn't talk about how they would actually be applied. If the fixes are being created after folks update/install the related app then they will have to manually trigger the updates to be applied.
Alternatively, either automatically, manually, or manually confirmed, a sha1 of the app fixes directory file list (with dates should be good enough) could be written to cache when applied. On boot steamtricks could compare the data directory for all installed games against their related hashs to see if they've changed. Once steam is quiet (ie might as well wait if it starts updating in first min or two) the updates could be triggered by requesting steam to validate the game.
The validation seems like best approach since it would clear any already applied changes and allow for a full re-application so that there is no need to try and diff with previous applied fixes or some nonsense. The only issue with that approach is whether an app validation can be triggered easily from outside the Steam UI, either via steam URL commands or perhaps tweaking a manifest file as they seem to track app states.
If system updates are run while steamtricks is running (probably common) that could be either detected via checking either the package version or a file in the root of data dir that contains the same and comparing against cache. Alternatively, the package could trigger a steamtricks command on postrun, but that is probably problematic since it would be running as root.
The text was updated successfully, but these errors were encountered: