https://bugs.winehq.org/show_bug.cgi?id=46226
--- Comment #4 from Austin English austinenglish@gmail.com --- (In reply to Olivier F. R. Dierick from comment #3)
(In reply to Austin English from comment #2)
(In reply to Olivier F. R. Dierick from comment #1)
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).
I don't think that's true at all. If a developer wants to ship a version of wine that they've tested against and support, we've never discouraged that.
I'm talking about bundling Wine with the Windows app in a single package. If the user wants to use another wine version, he should have the choice to not download or install the version from the app vendor. If multiple apps are compatible with the same wine version, it should be downloaded and installed only once. Bundling Wine with the app goes against modularity, reusability, bandwidth and disk space usage.
Yeah, that's what Google Picasa did.
It's also the likely result is someone ports their app with winelib.