[Bug 48955] New: Use xdg basedir spec

List overview All Threads

newer

older

[Bug 47883] New: Enable explicit...

[Bug 50058] New: Control (GOG)...

WineHQ Bugzilla

17 Apr 2020 17 Apr '20

5:23 p.m.

https://bugs.winehq.org/show_bug.cgi?id=48955

Bug ID: 48955 Summary: Use xdg basedir spec Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: riptide@mundo-r.com Distribution: ---

https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html

Instead of ~/.wine, configuration should be in the $XDG_CONFIG_HOME/wine/ and cache (safely-deletable files) should be in $XDG_CACHE_HOME/wine/. The big boxes files should be in the $XDG_DATA_HOME/wine/.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Show replies by date

WineHQ Bugzilla

17 Apr 17 Apr

5:24 p.m.

New subject: [Bug 48955] Use xdg basedir spec

https://bugs.winehq.org/show_bug.cgi?id=48955

riptide riptide@mundo-r.com changed:

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

WineHQ Bugzilla

5:24 p.m.

New subject: [Bug 48955] Use xdg basedir spec

https://bugs.winehq.org/show_bug.cgi?id=48955

riptide riptide@mundo-r.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |ArchLinux

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

WineHQ Bugzilla

10:09 p.m.

New subject: [Bug 48955] Use xdg basedir spec

https://bugs.winehq.org/show_bug.cgi?id=48955

Olivier F. R. Dierick o.dierick@piezo-forte.be changed:

--- Comment #1 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,

Wine should do this or that is a bit lacking.

Please provide some background, explanations or arguments to defend your idea.

Regards.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

WineHQ Bugzilla

11:09 p.m.

New subject: [Bug 48955] Use xdg basedir spec

https://bugs.winehq.org/show_bug.cgi?id=48955

--- Comment #2 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,

My opinion is that it would be impractical to split the wineprefixes in 3 parts and it's not worth the effort.

Support for XDG standard is application-specific design. Wine runs Windows applications. They are not XDG compliant and Wine can't do anything about it.

We could split 'well known' paths that theoretically contain config (registry files), cache (temp dirs) or data (ProgamData, Program Files, Windows) files, but the Windows application itself will never cooperate. It can put files anywhere. It's best to consider the wineprefix as a single, independent, hierarchy that follows the 'Windows' standard.

Keep in mind that ~/.wine is only the default wineprefix and most users have more than one wineprefix. How would Wine deal with multiple wineprefixes with those XDG_*_HOME settings?

What would become of the WINEPREFIX variable and things that depends on it/expect the files to be in a single location?

The use of single-directory wineprefixes is a long-standing thing and changing it will cause lot of trouble (Broken scripts and angry users) for no benefit at all. It'll require a global redesign of Wine's wineprefix management.

Not everyone wants to mix Wine stuff with their normal user files. Not everyone wants to use their XDG configuration for Wine stuff.

I'm sure they are other arguments against the use of XDG standard for wineprefixes.

If all you want is to unclutter your home directory by moving ~/.wine away, just put it wherever you want (in your XDG_DATA_HOME if you wish so) and set WINEPREFIX to the new location when invoking Wine.

Regards.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

WineHQ Bugzilla

11:17 p.m.

New subject: [Bug 48955] Use xdg basedir spec

https://bugs.winehq.org/show_bug.cgi?id=48955

Zebediah Figura z.figura12@gmail.com changed:

--- Comment #3 from Zebediah Figura z.figura12@gmail.com --- I don't think the request is to split up the prefix, which obviously can't be done, but rather just summarizing the XDG specification.

I don't think there's anything cacheable about wineprefixes, but it doesn't seem immediately unreasonable that the default wineprefix can still go in $XDG_CONFIG_HOME/wine or $XDG_DATA_HOME/wine instead of ~/.wine. Not sure which is appropriate.

The location of an explicitly specified WINEPREFIX would be up to the user; Wine doesn't automatically put a second prefix anywhere.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

WineHQ Bugzilla

18 Apr 18 Apr

1:16 a.m.

New subject: [Bug 48955] Use xdg basedir spec

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.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

WineHQ Bugzilla

6:36 a.m.

New subject: [Bug 48955] Use xdg basedir spec

https://bugs.winehq.org/show_bug.cgi?id=48955

Austin English austinenglish@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish@gmail.com

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

WineHQ Bugzilla

8:48 a.m.

New subject: [Bug 48955] Use xdg basedir spec

https://bugs.winehq.org/show_bug.cgi?id=48955

Anya animegirl@stronzi.org changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |animegirl@stronzi.org

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

WineHQ Bugzilla

9 Jul 9 Jul

7:30 p.m.

New subject: [Bug 48955] Use xdg basedir spec

https://bugs.winehq.org/show_bug.cgi?id=48955

soredake broaden_acid002@simplelogin.com changed:

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

166

Age (days ago)

1710

Last active (days ago)

wine-bugs@winehq.org

9 comments

1 participants

tags (0)

participants (1)

WineHQ Bugzilla