On (10:09 22/08/10), emmel <[email protected]> put forth the proposition:
What are the opinions on including the DIB engine patch in the build? It
has to be enabled manually anyway (environment variable WINEDIB=on), so
there shouldn't be any trouble, but it does fix some pointer issues with
a couple of programs.

Hi Emmel, will these patches find their way into upstream source in
due time? I am wary of fixing stuff that should be taken care of
upstream.

It's a multi part patch, but actually the
following sniplet seems to work nicely when placed directly before the
'chown -R root:root' (the autoconf is necessary):

mkdir dib
cd dib
unzip $CWD/dibeng-max.zip
cd ..
for i in `grep dib dib/series`; do
       patch -p1 < dib/$i
done
autoconf

The patch itself can be obtained from
http://bugs.winehq.org/show_bug.cgi?421 where it is usually the last
attachment. It's always called dibeng-max.zip, with the actual URL of
the download varying. As it's SBo policy to include patches with the
build script (I think) that shouldn't be too much of a problem, though.

I just had a look into this and none of the patches seem to
work with latest stable 1.2 release unless I'm missing something.
There is a series file which states the patches work against a GIT
commit. Perhaps they will work in the next release?

David

--
emmel <[email protected]>
GPG signed
Fingerprint: 60B4 D8E3 9617 900C 6726  168F D677 5AAD D40F CCE7
Certserver : hkp://pgp.mit.edu



_______________________________________________
SlackBuilds-users mailing list
[email protected]
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/



--
Don't look back, the lemmings are gaining on you.

Attachment: pgp5SUMo9d2MY.pgp
Description: PGP signature

_______________________________________________
SlackBuilds-users mailing list
[email protected]
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Reply via email to