http://bugs.winehq.org/show_bug.cgi?id=25044
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #12 from Alexandre Julliard julliard@winehq.org 2010-11-08 06:58:47 CST --- (In reply to comment #11)
Don't do that then. Create a wrapper script or something like that.
This sounds like a doctor responding "Don't do that then", when you describe some symptoms.
Only because there's workaround does not mean there is no bug, and I still consider this to be a (minor) bug, which should get fixed:
The behavior of the program should not be different when called as symlink than when being called "directly".
Who says so? If the app uses its path to locate files, then it makes sense that the behavior would be different if the launch path is different. Please don't reopen unless you can demonstrate that the app works fine on Windows when started through a symlink.