Wine troubles with wine32 and wine64

[doktor5000]

It's not a frontend, it's only the package which pulls either wine32 or wine64, but wine32 is the default.
As it was mentioned previously, just install wine and you are good to go.

@Ken: wine32 contains wine binary itself, and all dll's but without wine you will miss the windows fonts, and shared standard binaries like regedit, msiexec, regsvr32, wineserver, all man pages and icons and, most importantly, winecfg.

[Ken-Bergen]

@Ken: wine32 contains wine binary itself, and all dll's but without wine you will miss the windows fonts, and shared standard binaries like regedit, msiexec, regsvr32, wineserver, all man pages and icons and, most importantly, winecfg.

Interesting.
This is on a fresh Cauldron install but I installed the package wine which pulled in 110 packages including wine32.
I next installed wine64 which required the removal of wine.
I then ran

Code: Select all

urpme --auto-orphans

and winecfg and the wine man page are still there,
A packaging issue perhaps?

[jkerr82508]

The files that are in wine are also in wine64. For example:

Code: Select all

$ urpmf /usr/bin/winecfg
wine64:/usr/bin/winecfg
wine:/usr/bin/winecfg

and so if you have wine64 then you don't need wine, hence it is removed when wine64 is installed. I presume that this is so that you can have both wine32 and wine64 installed. I don't know if it is actually possible to run 32 bit and 64 bit Windows programs simultaneously. I've never had a need for wine64.

Jim

[doktor5000]

Could be, i've never really taken a look at wine64, only compared wine and wine32 previously.

[ftg]

I have seen this problem repeatedly, and while I do not know why it fails, I do know what causes it. It occurs when you need to reconfigure the ~/.wine directory from scratch. If you try to do it in place, or with something like

rm -fR .wine/*

you will have problems. If you remove the entire directory you will not. The reason is that ~/.wine contains hidden files that don't get removed in the first case.