Well, I don't know a thing about this and can't really give you any answers, but since you have a simple way to test it, you could do a "git bisect" to find the patch that caused this use of WINEPATH to stop working. That would at least tell you who made the change and give some idea of what changed and why. http://wiki.winehq.org/GitWine has instructions on doing that. On 8/3/06, Daniel Leaberry <leaberry@xxxxxxxxx> wrote:
Thanks for your response Vincent. Perhaps I was unclear. About 5 months ago I could run from a bash shell, export WINEPATH="/path/to/dll_dir_1" and running wcmd /c set would show that the PATH variable had the standard c:\windows\ wine paths but it would also have the paths I set in the WINEPATH variable in bash. It's this passing of the linux shell WINEPATH and appending it to the wine WINEPATH that seems to have disappeared. Thanks, Daniel
-- Vincent Povirk _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
