-
Notifications
You must be signed in to change notification settings - Fork 22
Update xlcore wine binary path #33
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
Open
travisbartholome
wants to merge
1
commit into
valarnin:xlcore
Choose a base branch
from
travisbartholome:fix-xlcore-wine-path
base: xlcore
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this logic cause issues with installations that were upgraded from an older version? e.g. does XLCore properly remove the old
betafolder?Alternatively, is there a reasonable way to just read the current path from XLCore's config somehow?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wiped my old wine prefix at some point while trying to upgrade so I can't fully confirm, but I think it doesn't remove the old wine in
betafolder. Reasoning: my original problem was that I updated XIVLauncher AUR package but not ffxiv-tools generated scripts, and then FFXIV was running on a much newer wine version than ACT, so I think the old path was still valid and ACT was trying to run on it.This is why the logic is looking for the new path first and falling back to the old one, rather than the other way around - so even if the old one is still there, we'll choose the new one. I think it should be safe but lmk if I'm missing a detail there.
Not sure if the path is stored directly in config but I think it's not if you use the default wine managed by xlcore (just says "Managed" in the config file iirc). I can confirm once back home in a couple days.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok yeah, confirmed that XLCore's
launcher.inijust containsWineStartupType=Managedfor this case, and no path info. Also looked around elsewhere and didn't see anything else.Seems hardcoding the path may still be the only option.