http://bugs.winehq.org/show_bug.cgi?id=25554
Summary: Could Wine live with empty WINEPREFIX? Product: Wine Version: 1.3.9 Platform: x86 OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: wylda@volny.cz
Hi, i use WINEPREFIX a lot, but when i tried to "delete" this variable by setting it to the empty string, wine then tells me:
wine: invalid directory in WINEPREFIX: not an absolute path
This empty string enhancement could help people like me, who don't know without google how to remove bash variable and want to quickly go with wine's default directory.
http://bugs.winehq.org/show_bug.cgi?id=25554
--- Comment #1 from Austin English austinenglish@gmail.com 2010-12-18 13:06:18 CST --- 'unset WINEPREFIX'
http://bugs.winehq.org/show_bug.cgi?id=25554
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv@dawncrow.de
--- Comment #2 from André H. nerv@dawncrow.de 2010-12-19 14:18:43 CST --- i just sent a patch: http://www.winehq.org/pipermail/wine-patches/2010-December/096958.html
http://bugs.winehq.org/show_bug.cgi?id=25554
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX
--- Comment #3 from Wylda wylda@volny.cz 2010-12-20 07:59:23 CST ---
WONTFIX: http://www.winehq.org/pipermail/wine-devel/2010-December/088310.html
Anyway, thanks André for care.
http://bugs.winehq.org/show_bug.cgi?id=25554
Andrew Nguyen arethusa26@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|WONTFIX |INVALID
--- Comment #4 from Andrew Nguyen arethusa26@gmail.com 2010-12-20 08:26:05 CST --- I don't believe it makes any sense to set WINEPREFIX to the empty string, so there was no defect in the first place.
http://bugs.winehq.org/show_bug.cgi?id=25554
--- Comment #5 from Wylda wylda@volny.cz 2010-12-20 13:06:38 CST ---
set WINEPREFIX to the empty string, so there was no defect in the first place.
But when you don't use WINEPREFIX, it's also empty. So i thought that correct handling coudl be fine, when explicitly set to empty.
http://bugs.winehq.org/show_bug.cgi?id=25554
--- Comment #6 from Andrew Nguyen arethusa26@gmail.com 2010-12-20 13:37:32 CST --- (In reply to comment #5)
set WINEPREFIX to the empty string, so there was no defect in the first place.
But when you don't use WINEPREFIX, it's also empty. So i thought that correct handling coudl be fine, when explicitly set to empty.
The WINEPREFIX environment variable not being set and WINEPREFIX being set to an empty string are two different conditions.
It makes sense for the user, most likely implicitly, to not state the location of the Wine prefix, in which case Wine defaults to ~/.wine. If the user explicitly requests a location represented by the empty string, however, Wine can't reasonably fulfill this request, so failing is a legitimate behavior.
Also, a minor issue that this behavior could catch is a defect in a shell script that exports WINEPREFIX but fails to set it to a reasonable value.
http://bugs.winehq.org/show_bug.cgi?id=25554
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Austin English austinenglish@gmail.com 2010-12-20 22:19:16 CST --- Closing.
-
wine-bugs＠winehq.org