http://bugs.winehq.org/show_bug.cgi?id=21513
Summary: Option to not inherit the UNIX environment Product: Wine Version: 1.1.37 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: dima@gmail.com
The Perforce command-line client (p4.exe) breaks because of a few environment variables that Wine inherits from the OS:
PWD: Doesn't even exist in Windows, and yet, p4 reads it and gets confused because it's a UNIX path, not a win32 one. P4EDITOR: I have it set to "nano", which makes sense for the Linux p4, but not the Windows one. P4DIFF: same as above.
p4 breaks the same way in WinXP if I set PWD to a UNIX-like path.
Since just about any UNIX environment variable can potentially break a Windows program, it would be nice to have an option to start programs with just the Windows environment. (While it's possible to run "env -i wine ...", that has some disadvantages: variables such as HOME, PATH, and DISPLAY need to be set, since they're required by Wine; if Wine starts a native program, that program won't get the original UNIX environment.)
Similarly, if Wine starts a native program, that program shouldn't inherit the Windows environment.
http://bugs.winehq.org/show_bug.cgi?id=21513
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |WONTFIX
--- Comment #1 from Vitaliy Margolen vitaliy@kievinfo.com 2010-01-27 20:15:07 --- That's what *NIX have programs like "env".
http://bugs.winehq.org/show_bug.cgi?id=21513
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #2 from Vitaliy Margolen vitaliy@kievinfo.com 2010-01-27 20:16:33 --- Closing - completely removing environment will cause more harm then good. If programs can't cope with some env vars - it's a bug in that program, since they will fail if you set those env vars on Windows.
http://bugs.winehq.org/show_bug.cgi?id=21513
--- Comment #3 from Dima Ryazanov dima@gmail.com 2010-01-27 20:19:09 --- I think I explained in the bug report why "env" isn't a good solution.
And, sure, it's a bug in the program - but in practice, it won't occur on Windows because Windows doesn't set those variables.
http://bugs.winehq.org/show_bug.cgi?id=21513
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|WONTFIX |
--- Comment #4 from Alexandre Julliard julliard@winehq.org 2010-01-28 04:55:51 --- It's quite reasonable to expect PWD to not be passed through, since it's a standard Unix variable.
The P4 variables clearly can't be handled in Wine, but you can always set the appropriate values for the Windows environment in the registry.
http://bugs.winehq.org/show_bug.cgi?id=21513
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #5 from Austin English austinenglish@gmail.com 2010-01-28 10:22:48 --- Confirming then.
http://bugs.winehq.org/show_bug.cgi?id=21513
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #6 from Dmitry Timoshkov dmitry@codeweavers.com 2010-01-29 00:43:20 --- Should be fixed by http://source.winehq.org/git/wine.git/?a=commit;h=2c0e31cfdcb2325c0d11ce07ec...
http://bugs.winehq.org/show_bug.cgi?id=21513
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Alexandre Julliard julliard@winehq.org 2010-02-05 11:39:23 --- Closing bugs fixed in 1.1.38.
http://bugs.winehq.org/show_bug.cgi?id=21513
--- Comment #8 from Dima Ryazanov dima@gmail.com 2010-02-05 22:45:50 --- I'm seeing an interesting behavior now. This is just what I wanted in this bug report, but I really doubt it's intentional:
Under HKEY_CURRENT_USER/Environment, create a string "FOO" with an empty value. Run "FOO= wine /c cmd set". Now, you see just the Windows environment, with no UNIX variables.
(What I expected was the usual environment, but without the FOO variable.)
Should I file a new bug for this?
http://bugs.winehq.org/show_bug.cgi?id=21513
--- Comment #9 from Alexandre Julliard julliard@winehq.org 2010-02-06 02:52:46 --- (In reply to comment #8)
Should I file a new bug for this?
Yes please.