Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%

brew install mame

local Homebrew formula metadata

MacPortsverifiziert · 94%

sudo port install mame

MacPorts ports tree · emulators/mame/Portfile · Quelle: api.github.com

Linux

Alpine Linux apkverifiziert · 92%

sudo apk add mame

Alpine Linux edge package indexes · mame · Quelle: dl-cdn.alpinelinux.org

Debian aptverifiziert · 92%

sudo apt install mame

Debian stable package indexes · mame · Quelle: deb.debian.org

Fedora dnfverifiziert · 92%

sudo dnf install mame

Fedora Rawhide package metadata · mame · Quelle: dl.fedoraproject.org

Nixverifiziert · 92%

nix profile install nixpkgs#mame

nixpkgs package indexes · pkgs/by-name/ma/mame/package.nix · Quelle: api.github.com

Arch Linux pacmanverifiziert · 92%

sudo pacman -S mame

Arch Linux sync databases · mame · Quelle: geo.mirror.pkgbuild.com

openSUSE zypperverifiziert · 92%

sudo zypper install mame

openSUSE Tumbleweed package metadata · mame · Quelle: download.opensuse.org

Überblick

Paketzusammenfassung

Multiple Arcade Machine Emulator

Projektlinks

Befehle und Aliase

mame

Verlauf

Projektgeschichte und Nutzung

MAME is a multi-purpose emulation framework whose stated purpose is to preserve decades of software history by documenting hardware and how it functions. Although originally the Multiple Arcade Machine Emulator, official documentation says it later absorbed sister projects and now covers arcade games, computers, consoles, calculators, and other vintage systems.

Projektgeschichte

MAME 0.1 was released on February 5, 1997. Early development moved quickly: MacMAME appeared in February 1997, X/MAME appeared in April 1997, vector-game support arrived in July 1997, and MAME32 also appeared in July 1997. The official history records a steady expansion from arcade CPU and sound emulation toward broader hardware documentation.

The project accumulated preservation infrastructure as it grew: CRCs for identifying ROMs in 1998, ZIP support in 1998, `history.dat` support in 1999, CHD support in 2002, and later major device-model and source-tree changes. In 2015 MESS merged into MAME, widening the project beyond arcade machines, and in 2016 MAME became GPL-2.0-or-later free and open source software with new documentation and licensing.

Adoptionsgeschichte

MAME has had a broad cross-platform packaging history, with official Windows binaries and source releases, Unix-like ports, macOS variants, and package-manager entries across Homebrew, Debian, Fedora, Arch, Nix, MacPorts, Alpine, openSUSE, and others. The project history page explicitly treats supported ROM set growth as one measure of project success.

For users, adoption is tied less to a single GUI and more to the shared command-line executable and data formats. Front ends, ROM managers, preservation workflows, and downstream OS packages all orbit the same MAME release stream and compatibility expectations.

Wie es verwendet wird

The ordinary package-manager workflow installs the `mame` executable, then users provide legally obtained ROM, disk, or media images separately. Official documentation emphasizes that copyrighted software images are not included and must be supplied by the user.

MAME reads configuration from INI search paths that differ by platform. Official command-line documentation lists default INI paths for Windows, macOS, and other platforms including Linux, making those paths important to packagers and users debugging why a setting is or is not being applied.

Warum Paket-Nerds sich dafür interessieren

MAME is package-manager lore because it is both an emulator and a preservation corpus interface. The package is just the executable and support files; the user's ROM sets, CHDs, artwork, plugins, shaders, and INI layers are separate data concerns.

For maintainers, MAME is a large C++ project with fast-moving compiler requirements, platform notes, bundled tools, and frequent releases. Small packaging differences around paths, SDL support, Lua/plugins, and INI locations can change user-visible behavior.

Zeitleiste

1997: MAME 0.1 released.
1998: MAME began using CRCs to identify ROMs and added built-in ZIP support.
2002: CHD support was introduced for hard-disk and other large media images.
2006: SDLMAME was released, improving Unix-like platform packaging.
2015: MESS merged into MAME.
2016: MAME became GPL-2.0-or-later free and open source software.

Related projects

MESS, the Multi Emulator Super System, was a sister project and was merged into MAME in 2015.
SDLMAME, MacMAME, MAME32, front ends, ROM managers, and MAME data files are part of the wider packaging and user ecosystem.

Quellen

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

narrow executable package without higher-risk signals

Signale

metadata:no-higher-risk-signals

Installationsverhalten

In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
Installiert mit 9 Laufzeitabhängigkeiten.
Build-Metadaten listen 4 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Linux: ~/.mame/mame.ini./mame.ini./ini/mame.ini
macOS: ~/Library/Application Support/mame/mame.ini~/.mame/mame.ini./mame.ini./ini/mame.ini
Windows: ./mame.ini./ini/mame.ini./ini/presets/mame.ini

Executables

Installierte Executables

Befehl	Art	Sichtbarkeit	Hinweis
`mame`	cli	globales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-10

Manager-Version0.288

Manager aktualisiert2026-06-22

lokale DatenOK

Upstreamnot checked

neueste erkannte Versionnicht erkannt

https://github.com/mamedev/mame

InfoNo cached GitHub release or tag data was available.https://github.com/mamedev/mamenone Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüssel	brew:mame
Version	0.288
Paketmanager	Homebrew
Paketmanager-Seite	https://formulae.brew.sh/formula/mame
Homepage	https://mamedev.org/
Repository	https://github.com/mamedev/mame
Upstream-Dokumentation	https://docs.mamedev.org/
Lizenz	GPL-2.0-or-later
Quellarchiv	https://github.com/mamedev/mame/archive/refs/tags/mame0288.tar.gz
Zuletzt aktualisiert	2026-06-22T14:05:26-07:00
Pulse	updated
Abhängigkeiten	flac, jpeg-turbo, portaudio, portmidi, pugixml, sdl3, sqlite, utf8proc, zstd
Build-Abhängigkeiten	glm, pkgconf, rapidjson, sphinx-doc
Von macOS bereitgestellte Bibliotheken	expat
Bottle	verfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install	nicht definiert
Dienst	keiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	mame
Version Scheme	0
Revision	0
Head Version	HEAD
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	head stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Debian apt95%

mame 0.276+dfsg.1-1+deb13u1

Multiple Arcade Machine Emulator (MAME)

mame mit Homebrew, apk, apt, dnf, MacPorts, Nix, pacman, zypper installieren