Windows package managers

[Firehawke]

MAME version

N/A

System information

N/A

INI configuration details

N/A

Emulated system/software

N/A

Incorrect behaviour

MAME cannot be currently found in WinGet or other package managers.

Expected behaviour

I should be able to run winget install MAMEdev.MAME and get an installation of MAME.

Steps to reproduce

N/A

Additional details

It's been a couple of years since I initially brought this up, and WinGet has improved substantially in that time.

I am aware that many of MAME's existing default behaviors (e.g. config file handling, file paths, etc) are not suited to a package manager setup at this time, thus this is to try to get MAMEdev to at least have a public discussion on this subject.

I won't even get started on the consistency and configuration headaches you run into switching Linux distros with the packager modifications being different-- that's an entirely different can of worms along with the subject of doing AppImage, Snap, Flatpak, etc.

[angelosa]

This genuinely needs to be moved to a discussion thread. On top of my head:

1. I'm definitely not convinced that WinGet should be first class citizen compared to any other package manager.
2. MAME UI/UX is just not ready and rather sketchy in places, particularly on non-Arcades.
3. Haiku actually have MAME versions released thru their HaikuPorts, it can be perfectly seen as a PoC about how non-existent our first time onboarding really is, which in turn already raises questions about bothering with any package manager at current time.

[angelosa]

As per #10084 (comment) I'm closing this out since it's same concept, reminding again to use a discussion thread to somewhere about the matter.