There's no reason why cedega's ebuild should block winex-transgaming's ebuild. The two install in entirely seperate directories and have entirely seperate launch scripts. Cedega still has a number of issues for some of the games I play that 3.3.2 doesn't have. It'd be nice to still be able to have 3.3.2 emerged so i can still use it when I need to.
coronalvr: what do you think ?
fine by me, what do you think?
AFAIK cedega and winex both have their config file ~/.transgaming/config and since they are quite different, with cedega having pixelshader options and all, there could be a quite nasty clash.
However, if you use point2play, it's a non-issue. Point2Play manages seperate WINE_PREFIX directories for each game. Also, winex/cedega does a pretty good job of managing changes to its config file on the fly anyways. Ideally, winex/cedega users should be managing seperate WINE_PREFIXes anyways if they don't use point2play. Installing multiple games into one WINE_PREFIX is just asking for trouble.
i don't see how it's necesarrily to have both installed at the same time .. or are there problems with some games & cedega that worked with winex 3 ?
With cedega 4.0.1 most of the compatibility problems I have are now ironed out. However, I have performance issues with regard to certain games running at high resolution (1600x1200). With winex 3.3.2 the performance problems don't exist. Traditinally with winex, a new release always causes some problem with an older supported game. While I understand not necessarily wanting multiple 4.x versions and multiple 3.x versions installed, there's no reason why cedega needs to block winex.
could be related to "wine-config needed" bug #9842
removed block since winex/cedaga dont kill each other
