https://bugs.winehq.org/show_bug.cgi?id=34166
alexchandel@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alexchandel@gmail.com
--- Comment #82 from alexchandel@gmail.com --- (In reply to Henri Verbeet from comment #77)
(In reply to Mike McQuaid from comment #73)
Given you officially support macOS as a platform, Apple haven't changed this, you recommend Homebrew as an installation method and there's a non-trivial number of Homebrew Wine users: is there any way you could consider merging this patch? As mentioned before I don't feel Homebrew maintainers are suitable for deciding whether a Wine patch is appropriate or not and getting things upstream benefits other macOS package managers and those who build from source on that platform. Thanks again!
I'm afraid I'll have to disappoint, it's really up to Apple to fix this. There may be architectural changes that may mitigate the issue in the future, but I can't promise that.
The thing is that the Apple OpenGL implementation has many more bugs and quirks than just this one, and while the individual workarounds for those may seem innocent enough on their own, those quickly add up to something unmaintainable. The other consideration is that Wine is primarily a Free Software project, and has comparatively few users and developers on MacOS. That means that even if we did include those kinds of workarounds, it would be relatively easy to inadvertently break them again.
I hate to break it to you, but wine has hundreds of thousands of macOS users. It's used in many universities and corporations with Apple hardware (more than you'd think, I know from experience), and generally by Apple users running Windows-only programs. The patch is applied universally, and this is a bug worth fixing.