Hide Forgot
wine.wow.i686 is provided in the x86_64-repo, and is needed for programs that require a 32-bit wineboot. However it can't cleanly be installed since it has conflicts with wine.x86-64. --> Processing Conflict: wine-1.3.10-1.fc14.x86_64 conflicts wine-wow(x86-32) = 1.3.10-1.fc14
This is not correct. wine-wow(x86-32) is _not_ needed on x86-64. If you install wine(x86-64) your wine will be able to run both 64bit and 32bit windows programs.
For normal cases I agree with you. However I had one installer that required to run dotnet20. Trying to install it myself (for 64-bit) I didn't succeed. Using the "winetricks"-script tried to install a 32-bit-version with an 64-bit wine, which didn't work. winetricks said that you might want to set WINEARCH=win32 and then give a separate WINEPREFIX to get a "win32"-wine running in parallel. That almost worked, but it needed wineboot for 32-bit. And that's in the wine-wow.i686-package. I wondered where the problem was with this since wine-wow is also provided in the 64-bit-repo and it doesn't seem to overwrite 64-bit-files afaik (one are in lib, the other in lib64).
It was stated on the wine64 pages that the contents of the wine-wow(x86-32) package should never be available on a prefix where a 64wow is running, hence the conflicts... You could always as a workaround install wine(x86-32) only and have a purely 32bit install...
But shouldn't it then conflict with wine-wow.x86_64 maybe, so you'd just have to install one or the other wine-wow? What would removing the "meta-package" (wine) help in this case? Anyway, thank you for the fast response on this.
The idea behind having the conflict in the meta package is this: For an ordinary user who wants to install wine (maybe as in the wine suite) a 'yum install wine' should install everything that is required for 'normal' wine operation. Users with special interests or in depth knowledge about wine could install the individual packages as they like w/o the wine meta package. See the conflict as a precaution so people do not install the 32bit wine-wow package on a standard wow64 setup as it normally should not be used and may cause strange bugs which then in turn require the wine folks or me to look at reports which are known to be broken. This logic would help in your case as well: Remove wine(x86-64) and install wine-wow(x86-32) without conflicts...