Hi... I am using the WineX ebuild 20020807 and it is really GREAT! It works perfectly and the /usr/bin/winex script is a very clever solution. I had only a few comments: 1) If you add this lines on the example ~/.winex/config file it will prevent a lot of little bugs: [Drive H] "Path" = "/usr/lib/winex/bin" "Type" = "hd" "Label" = "WineX" "Filesystem" = "win95" 2) A lot of games that works on WineX v1.03 doesn't work on the 2.1 version (ex:Balurs Gate). I will be very HAPPY if you create a winex1.ebuild that can exists together with WineX v2.1. 3) It is very useful and improves the speed of the emulation add the file /etc/env.d/81winex with the line LDPATH=/usr/lib/winex/lib Thanx a lot... Bernardo Silva
Hey... it is a very good Idea to UPdate the WineX with the working CVS version of QUARTZ, to let the game-cinematics runs... Bernardo Silva
winex-cvs is also available in portage. Please test it and let me know how it works for you. I will look at the config file for winex and possibly add this to it. I'll post on this report when I get to it this week.
Changes have been made to the configuration files for correct setting of PATH, LDPATH, and ROOTPATH and I added your drive H configuration to the default config file. The updated files should be in portage within 24 hours. We should still be able to get a winex version 1 build into portage but not until after our portage tree freeze is over. When I get the first build into portage I will leave another note on this bug report.
Report winex-cvs bugs/features to bug 7319 please. Just in case you need winex-1.0 right now, edit the winex-cvs ebuild and change the branch to the old version. -phoen][x- btw raker, i modified your wine ebuild - it goes to the new location (/usr/lib/wine) now. We should be fully fhs compliant. YAY!