Linked by Thom Holwerda on Mon 2nd Jul 2007 22:30 UTC
The issue between WINE and Parallels has been solved. "On July 2nd, Parallels sent the modified sources to me (Stefan Dosinger). I looked at them, and they are functionally mostly unmodified, except of some changes to get wined3d to compile on Windows(nameless unions, and similar things). What is yet to be verified is if these are the sources used to build the libs shipped in Parallels Desktop for Mac."
Permalink for comment 252439
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-06
Still, Parallels likely should have mentioned wine in the doc and how to get the source.
Excuse me, stop using FUD unless you actually *know* what it means - simply throwing it around removes any possible real impact of it when used in a real situation later on.
Regarding the issue at hand, they had over a month to resolve the situation - if they were investigating it, they should have mentioned it, if they were working on it, they should have mentioned it.
The problem with businesses is that they *FAIL* to communicate - they need to openly communicate and say, if they are going to take a x number of days, they should disclose that "yes, we used wine sources, however, we need to seperate the LGPL code from out own to ensure that we don't disclose proprietary third party or our own code".
This is just the tip of the iceburg; you get the same situation with Apple, Sun, and many other organisations - they need to disclose "this is where we are, this is where we're going - this is who we're partnered with, this is what we've used from the opensource community" - being secret squirl about this just brings to the forefront all sorts of conspiracy theories, and quite frankly companies involved only have themselves to blame.