[Slackbuilds-users] WINE / dib-engine patch

[emmel]

On Tue, Aug 24, 2010 at 09:46:37PM -0700, King Beowulf wrote:
> 2010/8/23 Ozan Türkyılmaz <ozan.turkyilmaz at gmail.com>
> 
> > 2010/8/23 emmel <the_emmel at gmx.net>:
> > > On Sun, Aug 22, 2010 at 02:30:51PM +0300, Ozan Türkyılmaz wrote:
> > >>
> > >> I don't know how Emmel sees it but I don't think they find their way
> > into
> > >> upstream due time. DIBEngine still needs a lot of work and So far
> > DIBEngines
> > >> were not cut for upstream quality.
> > >
> > > The way I see it I have to manually patch the slackbuild each time I
> > > build wine. Fact is these patches won't see there way into upstream
> > > anytime soon and that's the case for years, I think.
> > > The problem is not so much with the quality of the patches (which don't
> > > cause any problems I am aware of and will only come into play when the
> > > environment variable is set anyway), but structural decisions. From what
> > > I understand the DIB engine that ends up in release wine, some day in
> > > distant future, will be made right in respect to wine design guidelines
> > > and who knows what, requiring any number of changes to wine. It's more
> > > of a religious matters, I think, with some bits of maintainability mixed
> > > in. The code originally came from TransGaming...
> > > Still, there are quite a few programs out there (for me it's Uru, but
> > > have a look at http://appdb.winehq.org/viewbugs.php?bug_id=421) that
> > > require it, and it would be nice to at least have the choice, maybe with
> > > a configuration variable or something.
> > > Naturally, since I am not the maintainer I don't have the final say in
> > > the matter, but to make it short: It would be much appreciated and it's
> > > not patch that will end up in upstream anytime soone.
> >
> >
> > Still a patch that won't make it into uqstream soon should be part of
> > the SB script.
> > It causes problems here and there, well check out my git build scripts
> > for, I use
> > ddraw hack for some programs,  i use git for patching the source and
> > script for build.
> >
> > and DIBEngine is a problem which cannot solved easily, it's complex
> > piece of work,
> > it needs to work with any display driver it's thrown at, and not let
> > go of whet's not needed.
> >
> i can't speak for issues with other apps on the DIB bug list, but I haven't
> had any issues running Starcraft and BroodWar (CD version) since about 0.96
> or so even though they are listed as effected by the DIB bug.  i play quite
> a few games, some even listed as suboptimal in the apps database.  How well
> any game will play under wine is heavity dependent on which distro, graphics
> driver (and driver settings), and even the desktop GUI, as well ass numerous
> windows registry settings.
> 
> Interestingly enough, some of the wine "bugs" also effect native WinXP when
> playing the same Win95 or Win98 games so I say that the emulation is dang
> good.  (Oh wait...wine is not an emulator...).  Before I worry about
> patching wine for bugs, i do what Windows gamers have done since MS-DOS:
> tweak the graphics hardware and the windows registry, shut down nonessential
> services.

Well, Uru for one *does* need it. Can't play without a pointer.
-- 
emmel <the_emmel at gmx.net>
story archives available at http://ranira.wordpress.com
GPG signed
Fingerprint: 60B4 D8E3 9617 900C 6726  168F D677 5AAD D40F CCE7
Certserver : hkp://pgp.mit.edu
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20100825/6700cbc6/attachment-0001.sig>