Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prioritise Lutris spec's game path and platform over DB values #359

Merged
merged 2 commits into from
Jun 25, 2024
Merged

Prioritise Lutris spec's game path and platform over DB values #359

merged 2 commits into from
Jun 25, 2024

Conversation

nihaals
Copy link
Contributor

@nihaals nihaals commented Jun 24, 2024

See #209 (comment) and the commit messages for more context.

Editing the .exe path in Lutris only changes the .yml and not the database, so if in the future we actually set the `install_dir` in `scan_db`, we should make sure we still prioritise the .yml value.
It is unlikely that this would ever change for a game so it's less important to ensure that we're prioritising the correct source, but while we could likely try to infer the platform from what fields are used in the spec and what form they're in, the database contains an explicit value which is more likely to be used when deciding how to launch a game than an inference process.

We also never set `platform` in `scan_spec` so this is also a minor optimisation.
@nihaals nihaals changed the title Prioritise Lutris spec game path over DB game path Prioritise Lutris spec's game path and platform over DB values Jun 24, 2024
Copy link
Owner

@mtkennerly mtkennerly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@mtkennerly mtkennerly merged commit f536be3 into mtkennerly:master Jun 25, 2024
9 checks passed
@nihaals nihaals deleted the lutris-spec-db-merge branch June 25, 2024 11:36
mtkennerly added a commit that referenced this pull request Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants