https://bugs.winehq.org/show_bug.cgi?id=48955
--- Comment #4 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
I just can't consider the wineprefix as a whole as 'configuration'. Configuration is specific. XDG_DATA_HOME is more appropriate for many application binaries and windows libraries mixed with a few configuration files.
Moving '~/.wine' to "$XDG_DATA_HOME/wine" makes sense, but it'll break any derivative project that expects the historical default path of '~/.wine'.
Basically, anything that deals with Wine's wineprefixes would have to follow the XDG spec to find the default wineprefix location.
When $XDG_DATA_HOME is empty or not set, the default of '$HOME/.local/share' must be used. This makes two locations to check when WINEPREFIX is not set.
Wine could alleviate that by providing a command that returns the default path that would be used.
When WINEPREFIX is unset, the output of 'winepath "C:\"' can be parsed to get the default location, but it has issues: - Parsing is prone to errors (special characters in path come to mind); - It creates the wineprefix when it doesn't exists.
Unless there is already another command that I'm unaware of, winepath could be enhanced with a -d, --default, option that returns the default wineprefix path without creating it.
At least, if wine forces that change to other projects, they will know that they'll only have to do it once.
What about that complementary enhancement?
Regards.