Wine (originally an acronym for “Wine Is Not an Emulator”) is a compatibility layer capable of running Windows applications on several POSIX-compliant operating systems, such as Linux, macOS, & BSD. Instead of simulating internal Windows logic like a virtual machine or emulator, Wine translates Windows API calls into POSIX calls on-the-fly, eliminating the performance and memory penalties of other methods and allowing you to cleanly integrate Windows applications into your desktop.
Upstream has been contacted: https://forum.winehq.org/viewtopic.php?f=8&t=34721
Wine is pretty complex software and could be packaged in few different ways. Users and maintainers requested it for a long time from 2017 but never communicated loudly enough and all this turns in fragmented threads, polemics, debates, WineBaseApp proposals which was denied many times by Flathub admins and as the result is that there almost 2021 but we still doesn’t have Wine (and it derivatives) on Flathub. Also upstream never was even notified and no one even tried to communicate with upstream and ask to package Wine.
This is META thread for all Wine packaging related aspects on Flathub. The ultimate goal is to have Wine (and it derivatives) as standalone package and as reusable Wine build for 3rd party FOSS launchers such as Lutris, Legendary, q4wine, PoL, Legendary and such.
The oxymoron is that working Wine flatpak build was made for a long time by couple community members and flatpak manifest available in their repositories. It’s proven to work well and tested for decent period of time by group of people. This mean nothing is prevent to publish Wine right today if upstream don’t mind and not wait for decades approval of controversial proposals like WineBaseApp. Or if upstream will want to maintain it then this going to be perfect.