I just noticed that, for Wine on Leap 16.0 repositories, there’s only “wine” main package on oss repository, while on Emulators:Wine repository there’s both “wine” and “wine-wow64” packages.
What’s the difference between wine and wine-wow64?
Why isn’t wine-wow64 also on oss repository?
Thanks.
@F_style Hi wine on Leap 16.0 is only the wow64 version.
https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/16.0/html/release-notes-leap-160/index.html#id-wine
You might want to peruse the rest of the Release Notes…
Browsing default OSS repository:
https://download.opensuse.org/distribution/leap/16.0/repo/oss/x86_64/
search for package “wine” gives only wine and wine-staging, and corresponding devel packages.
Browsing Wine repository:
https://download.opensuse.org/repositories/Emulators:/Wine/16.0/x86_64/
search for package “wine” gives wine, wine-staging, wine-wow64, and corresponding devel and debug packages.
Yep.
So I an in my Leap 16.1 (in Beta) machine, with Myrlyn up on screen (doing activity NOT related to Wine), and thought I’d do a quick “wine” search … the screenshot shows what’s available on a → 16.1 ← default system:
.
@F_style what are you asking?
There is no 32bit support in Leap for wine, if you want 32bit then you need to use the flatpak version and enable the 32bit emulation. It’s all in the release notes.
What do you mean? Latest Wine can run 32 bit applications via its new wow64 architecture, according to upstream.
I’m asking what the difference between plain “wine” and “wine-wow64” packages is, and which one should I install.
There is no “wine-wow64” in openSUSE Leap distribution, just wine, which if you read the Release notes is the wine-wow64 version.
The released version in openSUSE Leap 16.0 is 10.10-bp160.1.15, does this version support 32bit?
In the default OSS repository certainly not, but there IS in the Wine repository:
https://download.opensuse.org/repositories/Emulators:/Wine/16.0/x86_64/
as I already mentioned in my post.
Strange … I’m back in Myrlyn again in my Leap 16.1 
Here’s what I see … I highlighted the important sentence
.
Personally, I would never have a need /desire to use Wine.
I do have a Windows-only laptop if I need to do Windows stuff. (which is very rare).
Did you not read what the release notes said?
openSUSE Leap includes wine 10.10, available only in the wow64 flavor. Users requiring 32-bit binary execution should consider using the Flatpak version or a similar solution.
There is no support for 32bit in Leap 16.0 aside from the emulation boot option.
I did, and they seem contradictory for me, because of what I already showed.
@myswtest doesn’t seem to have the Wine repository enabled.
Just because it’s called wine, it can be anything, in this case the name wine refers to wine-wow64…
Ok, I think I’m not being heard and this is going nowhere.
Thanks for your attention, and you can close the thread if you want.
Read what I wrote … no need
Anyway … we know what the “Leap 16” Wine version provides …
The issue at this point is that, beyond the “what is the difference” question …
You have NOT defined what it is you require.
To run Windows 32 bit programs in latest version of Wine.
But I already have the needed information. Thanks.
@F_style it won’t work, there is no 32bit capabilities/support in Leap 16.n series anymore…
The only way is flatpaks or distrobox, if you go the flatpak route then the 32 bit emulation boot flag needs to be set (In the release notes.)
I use Bottles flatpak which works fine…
I thought openSUSE’s Wine could still run 32 bit apps because of what upstream says about wow64 system, which can run 32 bit apps without 32 bit libraries, despite what openSUSE release notes say.
So this:
only applies for Wine Flatpak version?
@F_style yes for that link. Like I indicated, bottles seems to be a nice alternative as can split out an application to a bottle.
You can try the default wine, but does version 10 do what you expect?
I found a solution to no wine32 when I updated a few months ago (I needed to run my very old MSWord96 program).
First you need to enable 32 programs in the boot settings.
See:
You then need find a version of wine32 & wine64 in a repository, and change to these ones, you need to update the version of wine to these because wine64 was renamed to wine!
Like in:
https://download.opensuse.org/repositories/openSUSE:/Backports:/SLE-15-SP7/standard/
There are others as well.
I finally tested 2 32bit games in a 16.0 virtual machine. I tested all 3 different wines:
Wine from openSUSE OSS repo
Wine-wow64 from Emulators:Wine repo
Wine from Flatpak
The three of them behaved exactly the same:
with no ia32 emulation in kernel parameters I got the same error “nothing to run this application”
with ia32 emulation, all 3 worked!
Also, manually adding ia32_emulation=1 to Grub parameters and installing grub2-compat-ia32 package seems totally redundant: they do exactly the same thing! Then why do both things?
With this proof, I’d like to try asking again:
In OSS repo there’s Wine package; in Emulators:Wine repo there’s both Wine and Wine-wow64 packages. Wine-wow64 is actually almost twice the size of Wine package. So there should be a difference. What is this difference?
