Talk:Wine package guidelines

From ArchWiki
Latest comment: 5 August 2021 by CodingKoopa in topic Where to prepare environment

Where to prepare environment

When working with portable programs, this wiki recommends we copy/symlink files to "$HOME"/."$pkgname". This part of the guidelines appear to not have changed since 2007, and are (in my opinion) outdated. A more modern approach would be to follow the XDG Base Directory specs, and put them into "$XDG_DATA_HOME"/"$pkgname", which is usually in "$HOME"/.local/share/"$pkgname". This encourages a cleaner home directory, and a higher consistency $HOME and /usr.

I don't know what the procedure is to change package guidelines, so I would appreciate pointers.

VinceUB (talk) 09:43, 4 August 2021 (UTC)Reply[reply]

Yes, user-specific generated date belongs in "$XDG_DATA_HOME"/"$pkgname" if we are to follow the XDG Base Directory specs - which we should, and most existing packaging does (such as osuAUR). In addition to this, generated Wine prefixes should go in "$XDG_DATA_HOME"/wineprefixes/"$pkgname". This isn't an official Wine standard, but Winetricks respects this, and is the closest thing we have to a standardized location for Wine prefixes.
In the most convenient case, the program is available as a portable download which can be put in /usr/share or downloaded to ~/.local/share at runtime if really needed. In the more annoying cases, though, this won't be possible, and one might need to bundle a script that runs an installer to install the Windows program to "$XDG_DATA_HOME"/wineprefixes/"$pkgname". In that case, keeping everything in wineprefixes is probably acceptable, but it would be good to provide a symlink to direct "$XDG_DATA_HOME"/"$pkgname" to a sensible location within the Wine prefix. - CodingKoopa (talk) 07:14, 5 August 2021 (UTC)Reply[reply]