winetricks is inconsistent

[julianrichen]

winetricks seems to act very inconsistent in a number of the installers. Sometimes 32bit wine freaks out and breaks in 64bit prefix, and other times it doesn't. For example running winetricks --unattended d3dx9 will sometimes produce a return error of 1 with:

$ winetricks --unattended d3dx9
....
Executing wine regedit /S C:\windows\Temp\_d3dx9\override-dll.reg
wine: '/home/julian/.var/app/tld.domain.Application/data/wine-win64' is a 64-bit installation, it cannot be used with a 32-bit wineserver.
------------------------------------------------------
Note: command wine regedit /S C:\windows\Temp\_d3dx9\override-dll.reg returned status 1. Aborting.
------------------------------------------------------

While other times it works fine:

$ winetricks --unattended d3dx9
....
Executing wine regedit /S C:\windows\Temp\_d3dx9\override-dll.reg
Executing wine64 regedit /S C:\windows\Temp\_d3dx9\override-dll.reg
Using native override for following DLLs: d3dx9_31 d3dx9_32 d3dx9_33 d3dx9_34 d3dx9_35 d3dx9_36 d3dx9_37
Executing wine regedit /S C:\windows\Temp\_d3dx9\override-dll.reg
Executing wine64 regedit /S C:\windows\Temp\_d3dx9\override-dll.reg
Using native override for following DLLs: d3dx9_38 d3dx9_39 d3dx9_40 d3dx9_41 d3dx9_42 d3dx9_43
Executing wine regedit /S C:\windows\Temp\_d3dx9\override-dll.reg
Executing wine64 regedit /S C:\windows\Temp\_d3dx9\override-dll.reg

Simply deleting the /home/julian/.var/app/tld.domain.Application/data/wine-win64 directory and re-running the installer fixes it. Considering that flatpak is fairly reproducible this is probably an issue with winetricks.

It might be the way winetricks picks-up the platform type (Unix or Windows). Maybe I'm not setting a variable correctly before running?

---

Edit: I hate to duplicate work but I did play around with having winetricks equivalent installers as extensions to the Platform. So if you need d3dx9 you include org.winepak.Platform.Extension.d3dx9 with your manifest. Benefits also include data (like dlls, exes, fonts, etcs..) being pre-downloaded in a central place and during download process from the flatpak repo instead of during the installer. Tighter integration with flatpak and all that...

Not sure if it's the right way but might offer a better experience... need to experiment again now that I have a better understanding of extensions in flatpak.

[paulcarroty]

Winetricks for 64bit apps is totally broken for 99.9% of packages.

[julianrichen]

Ah... so rolling my own solution might indeed be better. I knew winetricks 64bit wasn't 100% finished but didn't know it still need a lot of TLC. More work but probably better in the long run.

Started play around with it tonight, will look more into it tomorrow. Thanks for the info.

[julianrichen]

winetricks will still be bundled with the Platform & Sdk, however, all future application that need some kind of downloaded package to be installed should be done via an Extension. Reasons:

• The experience has been much better
• flatpak is responsible for downloading the extra data instead
  • This avoids the *-installer file from hanging as it waits for a package to download, extract, and install as this wasn't apparent if you installed/first launched via the gui or GNOME Software/KDE Discover
• Unified cache

The application installer is still normally downloaded with curl in the installer so downloads aren't totally out of the installer but that is unavoidable atm. At least extensions are better handled.