There's been lots of progress in Wine lately; many important applications work better than ever. But the inevitable cost of such progress is that some applications are now broken and/or wine has odd problems.
For instance, as of the last two versions of Wine, StarUML can't be unminimized ( http://bugs.winehq.org/show_bug.cgi?id=12697 ), and as of 0.9.60, the IME support seems to be making wine apps run dog slow on at least one of my machines ( http://www.winehq.org/pipermail/wine-devel/2008-April/064999.html ). These seem like regressions that ought to be fixed before 1.0.
So... I guess my point is: the code freeze is starting soon, which is good; that will help coax developers into looking for and fixing recently introduced bugs rather than old ones. i.e. fight to hang on to what we've got (or had recently) rather than pushing to conquer new ground.
Those who absolutely have to work on risky new stuff in the meantime will increasingly have to keep their work outside the main tree for now. Once 1.0 is out, those patches can land, and the fight for new ground can resume.
On Sun, Apr 20, 2008 at 7:04 PM, Dan Kegel dank@kegel.com wrote:
There's been lots of progress in Wine lately; many important applications work better than ever. But the inevitable cost of such progress is that some applications are now broken and/or wine has odd problems.
Yes Office 2000/XP installs have totally regressed recently. While great improvements have been made for Photoshop and newer Office versions, it is frustrating that we are so close to Wine 1.0 and it might not even be able to install Office 2000.
Hi Dan,
2008/4/20, Dan Kegel dank@kegel.com:
There's been lots of progress in Wine lately; many important applications work better than ever. But the inevitable cost of such progress is that some applications are now broken and/or wine has odd problems.
For instance, as of the last two versions of Wine, StarUML can't be unminimized ( http://bugs.winehq.org/show_bug.cgi?id=12697 ), and as of 0.9.60, the IME support seems to be making wine apps run dog slow on at least one of my machines ( http://www.winehq.org/pipermail/wine-devel/2008-April/064999.html ). These seem like regressions that ought to be fixed before 1.0.
Worse still, after all of the work I've done on getting most tests running there have been 3 new failures in make test:
setupapi/devinst.ok devinst.c:831: Test failed: SetupDiEnumDeviceInterfaces failed: 00000103 devinst.c:850: Test failed: Unexpected path � devinst.c:920: Test failed: Expected ERROR_INVALID_DATA, got deadbeef devinst.c:925: Test failed: Expected ERROR_INSUFFICIENT_BUFFER, got deadbeef devinst.c:1013: Test failed: Expected ERROR_INVALID_DATA, got deadbeef devinst.c:1018: Test failed: Expected ERROR_INSUFFICIENT_BUFFER, got deadbeef msxml3/domdoc.ok domdoc.c:2323: Test failed: ret 80004005 domdoc.c:2327: Test failed: incorrect get_text string mshtml/dom.ok dom.c:1048: Test failed: Could not get {3050F4AE-98B5-11CF-BB82-00AA00BDCE0B} interface: 80004002
Is anyone working in these areas willing to look into the test failures?
Cheers,
Maarten.
-
Dan Kegel -
Maarten Lankhorst -
Steven Edwards