MAME 0.178 has been released: http://mamedev.org/releases/whatsnew_0178.txt I tried renaming the 0.174 ebuild to 0.178 but it doesn't work. It fails at the unpack phase. It seems there's an encoding issue with the contents of mame.zip: > mame/3rdparty/pugixml/tests/data/????????.xml: mismatching "local" filename (mame/3rdparty/pugixml/tests/data/????????.xml), > continuing with "central" filename version I'm going to report it on MAME Testers as soon as my account will be activated.
http://mametesters.org/view.php?id=6401
Created attachment 498800 [details] sdlmame-0.190.ebuild The attached ebuild kinda-sorta works for sdlmame-0.190 -- but not if I enable the tools useflag -- then it dies trying to build some player thing, anyone know what that's about? It solves the unpack issue like so: nonfatal unpack ./mame.zip || einfo "Ignoring wierd error" Which I figure is OK since the ebuild already successfully unpacked the inner-zip from the outer-zip into ${S}, without any error, before we get there. Why, in the name of all that is holy, is it packaged that way? Oh, well, I guess since the inner zip unpacking is not properly error checked, this kinda works out in our favor...
Is this latest version still Qt4 based, or did they port to Qt5?
According to http://docs.mamedev.org/initialsetup/compilingmame.html it seems that MAME needs Qt 5 now.
Old versions cleaned, this no longer is blocking Qt4 removal.
I'm currently using jorgicio's sdlmame-0.195 ebuild -> https://gpo.zugaina.org/Overlays/jorgicio/games-emulation/sdlmame - it builds and runs fine on my Gentoo Hardened amd64 box.
Could jorgicio's version not be put into mainline rather than removing this altogether??
Added this to my own overlay: https://github.com/gnu-andrew/gnu_andrew-overlay/commit/e57eb870d00ea0418ef99b932d4eebb7a44590e3 Can we please reconsider removing this?
Do you want to proxy maintain it? https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers As a side note: - games.eclass is deprecated for a long time, please drop its usage and install it in the same way as all the "regular" packages. That will also allow you to bump to eapi6 - You will also need to use xdg.eclass to fix bug 600324 - It seems that package would need to use python-single-r1.eclass instead of python-any-r1.eclass -> bug 616064 Thanks
removed