mame: portfile cleanup: small number of extraneous files included; remove older python variants

[mascguy (Christopher Nielsen)]

Presently, the 0.226 port of Mame includes a few things that need cleanup:

• Most notably, translation files included under ${prefix}/libexec/mame/language: Currently we include *.mo, as well as *.po and *.po~. Whereas only *.mo are needed. However, the extra files do not cause any issues with the software. And they are tiny... in the very low kilobyte range.
• Python variants cover versions 3.6 through 3.9. Remove support for 3.6, to simplify the port.
• Add a 'debug' variant.
• Reduce compilation warnings.

These issue will be fixed when the Mame project releases 0.227, or sooner if said release is delayed beyond December 2020.

[kencu (Ken)]

why disable 32bit build support? keep it all going if possible... mame builds and runs on 10.5 PowerPC last I tried. One day it might not, but if it still does, no need to throw that away I say...

[mascguy (Christopher Nielsen)]

Replying to kencu:

why disable 32bit build support? keep it all going if possible... mame builds and runs on 10.5 PowerPC last I tried. One day it might not, but if it still does, no need to throw that away I say...

The problem is that 32-bit x86 builds fail, due to compilation errors. And since it relates to the OpenGL headers, I suspect it might fail for 32-bit PPC too.

Of note, the last attempted buildbot job for PPC was last year, and it failed due to a dependency issue.

If you're interested in running a PPC build locally, I'd appreciate it! And if it succeeds, I'll happily keep 32-bit support for that architecture.

Your thoughts?

[mascguy (Christopher Nielsen)]

Just remembered that I still have an old PowerBook G4, running MacOS 10.5, which could be used for testing PPC 32-bit.

So if you think keeping PPC support makes sense, I'm happy to try building and running there. Let me know Ken!

[kencu (Ken)]

So in these circumstances, don't purposefully break/disable/remove/delete the 32bit build. mame built fine for me on 10.5 PPC last time I did it. Many people might come along and do the fix, if you don't/won't/can't. But if you strip everything out for no reason, it is that much harder to do.

Now it's different if there is something about the 32bit build, say, that is a deal-breaker for the 64bit bit build. If it comes down to one or other other, not both -- OK then, sacrifice the lesser. But here I don't sense that.

BTW -- totally ignore the 10.5 PPC buildbot -- it hasn't been working for nearly 2 years, so anything it might say is bogus confusion.

[mascguy (Christopher Nielsen)]

Replying to kencu:

So in these circumstances, don't purposefully break/disable/remove/delete the 32bit build. mame built fine for me on 10.5 PPC last time I did it. Many people might come along and do the fix, if you don't/won't/can't. But if you strip everything out for no reason, it is that much harder to do.

Absolutely Ken! The plan was to maintain all logic related to 32 vs. 64 bit in the portfile regardless. The only thing that was going to change, was supported_archs.

Now that we've chatted, I'll keep that list set to ppc ppc64 i386 x86_64. (Arm64 support is pending, and tracked by issue:61795.)

How does that sound?