If anyone is interested in having wine 64+32 bit and or the staging version, I took some time to make it happen.
However I will keep it unofficial since when looking at this:
It’s a refuse for valid reasons but whatever.
It might never end up in upstream.
Build it by yourself
git clone https://github.com/Nexolight/void-tainted-pkgs.git cd void-tainted-pkgs git checkout -b wine origin/wine ./xbps-src binary-bootstrap ./xbps-src -m masterdir-i686 binary-bootstrap i686 ./xbps-src -j $(nproc) pkg wine-staging (or wine) ./xbps-src -j $(nproc) -m masterdir-i686 wine-staging (or wine) sudo xbps-install --repository=hostdir/binpkgs/wine/multilib/ wine-staging-32bit (or wine-32bit) sudo xbps-install --repository=hostdir/binpkgs/wine/ wine-staging (or wine)
The order of the installation is important. Install the 32bit package always first. Same goes for reinstall. Otherwise it won’t work.
Don’t forget to setup your wineprefix before starting any app!
use the wine64 command. It will execute 32bit Programms just fine.
Note: I do apply wine-pba on wine-staging-3.6. It’s a patchset meant to improve performance for some games. you can disable it by changing /srcpkgs/wine-staging/template
Note2: If it tries to compile the dependencies (which will take forever), do:
git remote add upstream https://github.com/voidlinux/void-packages.git git fetch --all git pull --rebase upstream/master
If you use a ryzen cpu affected by the segfault issue replace $(nproc) with the amount of physical cores. and check dmesg for segfaults when the build fails.
For further help RTFM: https://github.com/voidlinux/void-packages/blob/master/Manual.md
Or just use the precompiled binary over my repository if you trust me
xbps-install -S --repository=http://void.coldbyte.net/wine/multilib/ wine-staging-32bit xbps-install -S --repository=http://void.coldbyte.net/wine wine-staging
The official repositories don’t have a wine-staging. So no need for xbps-pkgdb -m hold.