devel8421 at hotmail.com
Thu Oct 13 13:12:02 CDT 2005
There was a discussion here about 2 months ago, where I asked for a way to
embed WINE config strings into Win32 executable (for example, as string
resources). I was told that it is better to fix the problem rather than to
create workarounds, and that fixing bugs is trivial and takes at most 2-3
days as soon as it is reproducible.
I didn't argue much then but made a little experiment to prove my point. The
point is the following:
THE MOST DIFFICULT THING IN GETTING BUG FIXED IS TO GET SOMEBODY WORK ON IT.
The same applies both to commercial environments and to open source ones
illustrates it very well:
I've found an application that experiences the problem with sympthoms which
are very similar to ours,
can be installed in 5 minutes and the problem can be reproduced in 3 clicks.
And I've opened a bug in
WINE's bugzilla: #3270 (another one #3269 was opened for another
incompatibility). Result is the following: IN 6 WEEKS NOBODY EVEN TOOK A
LOOK AT BOTH THOSE BUGS.
Welcome to the real world
FREE pop-up blocking with the new MSN Toolbar get it now!
More information about the wine-devel