Define WINEPREFIX if it doesn't exist

[Alexandre Julliard]

"Dmitry Timoshkov" <dmitry at baikal.ru> writes:

> But in order to read ~/.wine/config WINEPREFIX should be either already
> detected or any default value used. Why not use that value everywhere
> else? After all, what is the problem with using a default value, which
> actually is being already used?

The problem is that you can't depend on it being set, because Wine is
supposed to work fine without it. Setting it in the wrapper script
won't change that, because the wrapper is only used when running from
inside the source tree.

> But that would effectively invalidate all the efforts to make Wine easily
> configurable. There are situations when somebody wants by changing single
> environment variable get completely different Wine environment: with distinct
> registry, config, win.ini, .ppd and other files...

On the contrary, it's even easier to configure if you don't have to
install generic.ppd at all and it just uses the global one. You could
still specify it in the config file if you really wanted, but you
shouldn't have to. Of course if you want multiple Wine environments
with different generic.ppd files then you need to tweak the config;
but that's definitely not the standard case.

-- 
Alexandre Julliard
julliard at winehq.com