https://bugs.winehq.org/show_bug.cgi?id=53393
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #4 from Zeb Figura z.figura12@gmail.com --- Wine is fundamentally a piece of multiarch software, because Windows is too, and this will only become more true as time goes on and we improve our WoW64 implementation. (Although, from a packaging perspective, when WoW64 is done, distributions can use it, and then they won't need to depend on 32-bit host packages except for the 32-bit MinGW compiler and optionally some 32-bit MinGW libraries.)
I understand it's unfortunate that we have to do things differently, but if there are exceptions to be made, Wine should quite reasonably be one of those.
It's worth pointing out, also, that while a build of Wine gutted of 32-bit components *can* work with purely 64-bit software, I don't think we want to distribute that, lest unwary users fail to install the 32-bit portion and wonder why things won't work. I think it makes more sense to require manual configuration, as you've done, if you're really sure that you don't need the 32-bit parts. (It's also worth pointing out that even 64-bit programs often ship with 32-bit installers, since otherwise the program has no way of controlling what happens on a 32-bit machine.)