On Fri, Sep 25, 2009 at 05:28, Sven Eckelmann wrote:

Hi,

...

Note the comment about the yasm dependency.  It appears this is a hangover from older mupen64plus versions that did require it (my bad...).  When you rebuild to remove that, you will obviously need the build fix patches from the Debian patch tracker (glibc2.10, as-needed) and I would also include the ones to build against the system libraries. I would recommend to take patches from my git repo[3] as the patch tracker is (for unknown reasons) complete outdated.

I think he meant following patches:  * as-needed.patch  * ftbfs-glibc210.patch  * system-libbz2.patch  * system-liblzma.patch  * system-libpng.patch  * system-zlib.patch

Fixes of crashes and glitches:  * fix-7z-subfolder.patch  * fix_readpng.patch  * gtk-open-filter.patch  * jttl_fix_romclosed.patch  * rice-screenflickering.patch  * rice-texturepack-crash.patch  * version-string.patch

Experimental patches are:  * xdg-basedir.patch  * noexecstack.patch

Mostly debian specific (or on architectures you don't support):  * dejavu-font.patch  * default-optimisations.patch  * destdir.patch  * fix-desktop-file.patch  * ftbfs-kfreebsd.patch  * ftbfs-dynarec.patch  * debian-archs.patch  * glide64-noasm.patch  * plugin-searchpath.patch  * remove-gln64.patch  * remove-nondfsg-icons.patch  * static-binutils-libs.patch

Only debugger related (not activated on Arch)  * ftbfs-debugger.patch  * rice_nodebug.patch

There is also a glitch which prevents the correctness of the pure interpreter (haven't checked yet the interpreter and recompiler) submitted upstream as bug 272. Maybe you have an idea for bug 51. I am digging a little bit around but without any real success - only got a hack which can be used to open the gate and then restart the game with a non-hacked version of mupen64plus.

Before I forget: When you change the PKGBUILD - can you please change the maintainer field? I just send Allan McRae that mail because he was marked as maintainer of that package.

Best regards,        Sven

...

[3] http://git.debian.org/?p=collab-maint/mupen64plus.git;a=tree;f=debian/patche...

I don't really know.. To be honest I don't actually use the software actively, and I wouldn't know where to begin with selecting how/if it should be patched. Maybe another TU would like to take over the package from me?