"Dmitry Timoshkov" <[EMAIL PROTECTED]> writes: > I'm not sure what do you mean by "the right thing" here. Do you mean that > I'm not allowed to use WINEPREFIX in the config, or you mean that every > single dll should have its own ExpandEnvironmentStrings implementation? > Something else?
Well, you cannot use WINEPREFIX in the config file that is in ~/.wine/config, since it can potentially be used without the prefix being set. The easiest is to replace %WINEPREFIX% by %HOME%/.wine in that specific config file. A more elaborate solution would be to make wineps look in the prefix dir when it gets a relative dir, like the drive config code does. I'm not convinced we want to do that though, IMO it would be better to install generic.ppd globally and make wineps default to something like $(libdir)/generic.ppd. -- Alexandre Julliard [EMAIL PROTECTED]
