http://bugs.winehq.org/show_bug.cgi?id=5908
Dan Kegel <dank(a)kegel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WORKSFORME |FIXED
--- Comment #10 from Dan Kegel <dank(a)kegel.com> 2009-12-07 12:09:27 ---
Let's use 'fixed' so Alexandre's announce script picks it up.
We have two weeks to retest before the next release to make sure that's
accurate.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=6971
--- Comment #288 from Tomasz Sałaciński <tsalacinski(a)gmail.com> 2009-12-07 12:06:47 ---
(In reply to comment #287)
> Then someone should step up and organize the "hacks" in a Wiki entry, so that
> you can decide which one to use for a specific situation / game / application.
> Obviously this has to be someone else than Vitaliy.
Something that may be called winehacks.org? :> I understand Vitaliy's approach,
because neither users or developers want "hacky" code in WINE. But, there are
some other hacks in WINE that work for now (fallback to X server - DIB engine
not present). IMHO discussion about hacks should be somewhere else, maybe there
should be another section like "Hacks" in WINE's website menu? With information
that WINE developers DO NOT SUPPORT these hacks and if someone is using hacked
WINE must not post bugs. This could help some people to play the game they
really want without thinking that their copy of wine won't run another game
because they don't really want to play it.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=6971
--- Comment #287 from Tobias Jakobi <liquid.acid(a)gmx.net> 2009-12-07 11:53:23 ---
Then someone should step up and organize the "hacks" in a Wiki entry, so that
you can decide which one to use for a specific situation / game / application.
Obviously this has to be someone else than Vitaliy.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=5908
Juan Lang <juan_lang(a)yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
--- Comment #9 from Juan Lang <juan_lang(a)yahoo.com> 2009-12-07 11:27:25 ---
This works for me. Commit 497b67dbf623e8aacb2eaaaa326a5782eb3c06d8 fixed the
installer bug. Please reopen if it's still failing for you.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=5908
Bug 5908 depends on bug 12014, which changed state.
Bug 12014 Summary: Ability installer crashes in crypt32
http://bugs.winehq.org/show_bug.cgi?id=12014
What |Old Value |New Value
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=6971
GreatEmerald <pastas4(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pastas4(a)gmail.com
--- Comment #286 from GreatEmerald <pastas4(a)gmail.com> 2009-12-07 11:11:43 ---
Indeed, this is a very serious bug that affects entire game engines and make
them for the most part frustrating to use. Anything that can improve the
situation should be welcome, whether they are hacks or not.
Though I do agree that the attachment list is cluttered and could be a lot
better organised, since right now there are a lot of patches to choose from yet
there isn't much information on what they do and what they don't.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=6971
--- Comment #285 from Tobias Jakobi <liquid.acid(a)gmx.net> 2009-12-07 11:04:01 ---
(In reply to comment #282)
> People please keep this dirty hacks outside of bugzilla. And do not turn it
> into a forum for clueless people about how to compile Wine!
Don't you think it's a bit arrogant to be the one to define what's a dirty hack
and what is not?
If everything that resembles a hack should disappear from wine we could deleted
a large percentage of the codebase - see e.g. the current discussion about the
soundsystem on the mailing list.
Considering how long this bug here has existed and considering even more the
time it will STILL exist, it's VERY counterproductive to discourage the
creation of such (what YOU call) "hacks"....
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=6971
--- Comment #284 from haarp <liquitsnake(a)gmx.net> 2009-12-07 10:49:24 ---
(In reply to comment #282)
> People please keep this dirty hacks outside of bugzilla. And do not turn it
> into a forum for clueless people about how to compile Wine!
Sorry, but I don't think that's the right thing to do. I agree with the help
forum part. But disallowing 'hacks' is not really the right course If you ask
me.
People come here looking for progress and solutions for their problem. The real
fix is still months (years?) away and you can't expect them to wait for that
long. The hack is a temporary solution. Hacks get posted in other bugs every
day. Hell, even Wine itself already contains a 'force' hack. force-box is
simply the logical extension of that, and works well so far for many people. I
don't see why it should be forbidden.
Yes - it's no proper fix. The current Wine philospohy is not to adopt such
things. I accept that. But for the sake of completeness, keep it in Bugzilla.
I know that you, Vitaliy, have far more experience on that matter than anybody
else. I'm not doubting your authority on this. But I don't agree either.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=6971
--- Comment #283 from Clarence Risher <sparr0(a)gmail.com> 2009-12-07 10:48:18 ---
I concur on the subject of compilation instructions.
However, I disagree regarding patches/hacks. If there is a bug that affects 5
games, and we have no global solution, where other than in that bug report do
you suggest keeping the 5 distinct-but-related patches that solve the problem
in thos particular games? Assuming that the contents of the patches are of use
to a developer who might finally fix the bug, keeping them on 5 separate appdb
pages seems counterproductive.
Also, marking the patches obsolete is both inaccurate and spam-generating.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.