https://bugs.winehq.org/show_bug.cgi?id=46226
--- Comment #1 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Are you asking that the dll.so libraries be provided in separate packages?
I see two issue with that:
1. If you replace a dll.so file with another from a different source, you'll run into ABI incompatibilities between the dll.so and the wineserver executable.
2. Multiple wine packages can be installed at once. Users will have a hard time installing library packages for the appropriate wine package.
Overall, I don't see the benefit of such a 'pluggable' dll.so architecture.
Just install the one or two custom wine packages that you need for your apps and you'll be going.
App developers/packagers should NEVER package wine with their app but provide instructions or automate the installation of the wine package from its repository (official or custom).
Users testing third party wine by trial and error is good for them but useless for developers: Most third party wine use hacks and that's why they stay out of official wine.
And if an app doesn't run with official wine, file a bug report (if there isn't one already). Fixing bugs in official wine is better than requiring the use of custom wine packages.