Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#35213 - [q4wine] Env Var $WINEPREFIX Ignored for Package Install
Attached to Project:
Community Packages
Opened by Dave (DaveCode) - Sunday, 12 May 2013, 05:57 GMT
Last edited by Sergej Pupykin (sergej) - Saturday, 16 November 2013, 18:38 GMT
Opened by Dave (DaveCode) - Sunday, 12 May 2013, 05:57 GMT
Last edited by Sergej Pupykin (sergej) - Saturday, 16 November 2013, 18:38 GMT
|
Detailsq4wine 1.0_r3-1 (x686)
A prior WINE installation lived here when q4wine was installed. echo $WINEPREFIX /home/Windows Now that folder is not the same as $HOME. They are separate folders. The q4wine setup wizard didn't read $WINEPREFIX or even $TERM (most people use urxvt, not xterm). I couldn't find how to tell q4wine about an extant $WINEPREFIX as the "Default" one. It should have detected $WINEPREFIX and made it the Default. It should also use proper FreeDesktop.org $XDG_... vars. I have the impression this app just uses hardwired paths in its code. Thanks for maintaining the package. Good work. |
This task depends upon
Closed by Sergej Pupykin (sergej)
Saturday, 16 November 2013, 18:38 GMT
Reason for closing: Upstream
Saturday, 16 November 2013, 18:38 GMT
Reason for closing: Upstream
Comment by Sergej Pupykin (sergej) -
Tuesday, 14 May 2013, 12:32 GMT
Did you notify q4wine developer?