http://bugs.winehq.org/show_bug.cgi?id=6506
------- Additional Comments From zthg4821@gmail.com 2006-24-10 10:27 ------- Thanks for taking the time to respond Mike.
For Wine, 'critical' means "Wine does not start at all on my platform.
That's not what your Bugzilla says:
----------- Severity This field describes the impact of a bug.
Blocker Blocks development and/or testing work Critical crashes, loss of data, severe memory leak Major major loss of function Minor minor loss of function, or other problem where easy workaround is present Trivial cosmetic problem like misspelled words or misaligned text Enhancement Request for enhancement -----------
Let's see how bug 3063 fares against that definition of "critical":
* "crashes" - Check! * "loss of data" - Check! * "severe memory leak" - Check!
Please don't let the officially given definitions be of inconvenience. Feel free to ignore them when, for example, the situation threatens to delay the release of a Codeweavers or TransGaming product or otherwise put a dent in revenue or tie up company resources. As the accountants and shareholders will tell you, Wine's significant deficiencies when used with a single (as far as you know) application just isn't worth the expense to fix. :)
There are native applications such as Amule which can replace emule's functionality, so I have a hard time to believe that this is stopping you from doing something.
I'm surprised to hear such reasoning coming from a Wine dev. If you really want to go there then you must concede that ~99% of popular Windows applications (not just eMule) can be substituted with native *nix apps for ~99% of users. Most people don't use Wine because they have no other choice, they use it because they want to use the applications they most prefer. So when users reach for Wine they expect it to work. It's disingenuous to place part of the blame on the user for daring to use Wine for what it was designed to be used for.
-
Wine Bugs