On 02/09/2014 10:40 AM, Jonathan Aquilina wrote: > https://sourceforge.net/p/lmms/bugs/573/ > > Basically there seems there is a fix for this issue in terms of the upstream > wine. > > The problem is there are no packages in the wine ppa yet and it involved the > person compiling wine from source. > > I am wondering though if we should include the wine source somewhere in our > tree, that way it makes for less issues for someone to figure out what vst > dependencies are missing, but also allows us to easily control versions of > wine that are being used. > > As all distros do not use the same version it will allow us to distribute > wine > with this project. >
No, we shouldn't. That'd just lead to conflicts and problems when people already have Wine installed, and some people may not care about VST's and not want to use Wine at all. Also it'd cause needless bloat in the package. All that just to solve a relatively marginal problem. Packagers would likely just strip away the Wine anyway to prevent issues, so it'd be a pointless exercise in the end. We have to remember that we're nowhere near the only software using Wine out there. ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk _______________________________________________ LMMS-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmms-devel
