On Tue Jan 27 09:19:12 2026 +0000, Loïc Rebmeister wrote:
I think making wine-mono dlls part of wine-mono makes sense unless the dll might get called in a context where wine-mono isn't loaded. But putting C only dlls in wine for wine-mono also makes sense since it might reduce developer burden, and ensure the dlls are compatible with the latest version of wine and would allow to use the current wine testing infrastructure. Transferring all wine-mono dlls in wine would greatly reduce maintenance efforts on wine-mono at the cost of portability. Transferring all wine-mono dlls in wine-mono would greatly increase portability at the cost of maintenance. By portability, I mean between wine versions. Everything is a trade-off, I think reducing required maintenance effort is worth it if it gives developers more time to do other stuff! Note: I am not worried about proton as Valve backport any required dlls to their wine version if needed!
-- https://gitlab.winehq.org/wine/wine/-/merge_requests/9958#note_128128