[Package]: x86_64 wine in aarch64 repos for using with box64.

[twaik]

Why is it worth to add this package?

I know it is quite complicated but I think it is possible to build x86_64 wine for aarch64 environment. We can build Wine and all its dependencies with ARCH=amd64 TERMUX_BUILD_IGNORE_LOCK=true (to invoke building from within wine's build.sh) and somehow override TERMUX_PREFIX to something like TERMUX_PREFIX="$TERMUX_PREFIX"/libexec/wine_x64/ to avoid prefix interference and disable packaging for nested builds. After building wine and all its dependencies we can pack everything to a single package called like wine_x64 and limit building only to aarch64 (because this package will be used only there. In this case people will use only our solution and not other solutions and not third parties.

Home page URL

https://www.winehq.org/

Source code URL

https://dl.winehq.org/wine/source

Packaging policy acknowledgement

• [X] The project is actively developed.

• [X] The project has existing packages and is "well known".

• [X] Licensed under an open source license.

• [X] Not available through a language package manager: pip, npm, cpan, cargo, etc.

• [ ] Not taking up too much disk space (< 100MiB per architecture, exceptions can be made)

• [ ] Not duplicating the functionality of existing packages.

• [X] Not serving hacking, malware, phishing, spamming, spying, ddos functionality.

• [X] I certify that I have read Termux Packaging Policy and understand that my request will be denied if it is found lacking.

Additional information

I know I did not check taking too much space and duplicating functionality. But this case is pretty much special.

[twaik]

@Maxython we had a short talk about this in discord, probably you remember it.

[IntinteDAO]

Is there a major difference between Wine with box64 and Hangover Wine, which uses box64 but on the Wine side?

On the other hand, the more solutions the better. It is worth remembering that Wine is already in TUR.

[twaik]

Hangover is maintained by other person. So in the case of using it we will be able to ask for help only in hangover repos. In the case of problems with mainstream wine we can ask for help in official Wine channels. Also it is considered to be as stable as official wine on x64 machines (of course taking into account it is running on top of x64 translator).

Wine is already in TUR

Wine is already in main repo, but it is not really usable on aarch64 (most devices running termux are aarch64) without x64 translator. Packaging separate wine amd64 for aarch64 devices will let us use it without 3rd party solutions like mobox, winlator, box86droid, etc.

[IntinteDAO]

Hangover is maintained by other person. So in the case of using it we will be able to ask for help only in hangover repos. In the case of problems with mainstream wine we can ask for help in official Wine channels. Also it is considered to be as stable as official wine on x64 machines (of course taking into account it is running on top of x64 translator).

Wine is already in TUR

Wine is already in main repo, but it is not really usable on aarch64 (most devices running termux are aarch64) without x64 translator. Packaging separate wine amd64 for aarch64 devices will let us use it without 3rd party solutions like mobox, winlator, box86droid, etc.

In my opinion, you're right, but not quite right either. Of course, it's nice if there will be Wine with box64 without Hangover. However, more and more applications are running natively on ARM64. I even wondered if we should make repositories like "TUR for Wine".

Of course, you are one of the package creator, so even if I cast spells, you will do what you want, because this is actually a good thing. So I can pray that you succeed.

Although you can always look behind other things that would also help Wine, namely better GPU acceleration (unfortunately the one in Termux works, but badly). That would be a cool revolution.