macOS
Homebrew Caskverifiziert · 100%
brew install --cask amiberrylocal Homebrew cask metadata
cask
amiberry mit Homebrew Cask installieren
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für amiberry in AI-Agent-Workflows.
Installation
Weitere Installationsbefehle
Überblick
Paketzusammenfassung
Amiga emulator
Projektlinks
Befehle und Aliase
In der lokalen Paketdatenbank wurden keine Executable-Aliase gefunden.
Verlauf
Projektgeschichte und Nutzung
Amiberry is a GPL-licensed, multi-platform Amiga emulator built on the WinUAE core. It targets systems ranging from low-power ARM boards to modern desktop workstations and supports floppy, hard-drive, CD, WHDLoad, save-state, and machine-configuration workflows.
Projektgeschichte
Amiberry was forked from the UAE4ARM-RPi project and evolved into a separately named Amiga emulator. It incorporates the WinUAE emulation core while adding platform ports, performance work, JIT implementations, a modern GUI, controller integration, and automated WHDLoad workflows.
Adoptionsgeschichte
Amiberry initially emphasized ARM single-board computers, including Raspberry Pi-class systems, before expanding into a multi-platform emulator for Linux, macOS, Windows, Android, FreeBSD, and Haiku. Official distribution now includes native packages, Flatpak, AUR, Homebrew Cask, installers, portable archives, and direct release artifacts.
Wie es verwendet wird
Users supply legally obtained Amiga Kickstart ROMs, select an emulated Amiga model, and load disk, CD, hard-drive, WHDLoad, or `.uae` configuration files. Quickstart presets cover common machines, while advanced users tune CPU, chipset, display, input, storage, shaders, and JIT settings or launch media from the command line.
Warum Paket-Nerds sich dafür interessieren
Amiberry connects several package-culture niches: retro-computing preservation, emulator packaging, low-power ARM systems, desktop application bundles, and ROM-dependent software that cannot bundle all required proprietary firmware. Its platform-specific directory model and portable mode are particularly relevant to packagers maintaining upgrades without losing configurations.
Zeitleiste
- 2017: The 2.8 beta line recorded the transition from UAE4ARM naming to Amiberry and the fork from UAE4ARM-RPi.
- 2020: The 3.x and 4.0 era expanded WinUAE synchronization, WHDLoad automation, hardware targets, and desktop-oriented functionality.
- Current distribution: Amiberry supports Linux, macOS, Windows, Android, FreeBSD, and Haiku.
Related projects
- WinUAE supplies the upstream emulation core. UAE4ARM-RPi was the project from which Amiberry was forked. Amiberry Lite preserves a lighter WinUAE-based variant for slower hardware, while WHDLoad integration provides automated launching of installed Amiga software.
Quellen
- Official README: https://github.com/BlitterStudio/amiberry#readme
- Official directories reference: https://github.com/BlitterStudio/amiberry/wiki/Amiberry-directories
- Official version history: https://github.com/BlitterStudio/amiberry/wiki/Version-history
- Official website: https://amiberry.com/
Sicherheitslage
Noch keine Protected-Tool-Abdeckung gefunden
Für amiberry wurde kein passendes lokales Secret-Handling-Manifest gefunden. Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.
Installationsverhalten
- In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
- Es wurden keine Homebrew-Bottle-Metadaten erfasst.
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
~/.config/amiberry/amiberry.conf~/Amiberry/conf/*.uae- macOS
~/Library/Application Support/Amiberry/amiberry.conf~/Documents/Amiberry/Configurations/*.uae- Windows
%LOCALAPPDATA%\Amiberry\amiberry.conf%USERPROFILE%\Amiberry\Configurations\*.uae
Executables
Installierte Executables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
| Es waren keine Executable-Daten vorhanden. | |||
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-11-04
Manager-Version8.5.0
Manager aktualisiert
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt
https://github.com/BlitterStudio/amiberry
- InfoNo package-manager update timestamp was available.niedrig Konfidenz
- InfoNo cached GitHub release or tag data was available.https://github.com/BlitterStudio/amiberrynone Konfidenz
Installationsmetadaten
Paketmetadaten
| Paketschlüssel | cask:amiberry |
|---|---|
| Version | 8.5.0 |
| Paketmanager | Homebrew Cask |
| Paketmanager-Seite | https://formulae.brew.sh/cask/amiberry |
| Homepage | https://amiberry.com/ |
| Repository | https://github.com/BlitterStudio/amiberry |
| Upstream-Dokumentation | https://amiberry.com/ |
| Quellarchiv | https://github.com/BlitterStudio/amiberry/releases/download/v8.5.0/Amiberry-8.5.0-macOS-universal.dmg |
| SHA-256 | 002bb71af68a86a23c2779258248af71683c6a56caf74cf716e40081b5df9e7a |
| Bottle | nicht erfasst |
| Homebrew post-install | nicht definiert |
| Dienst | keiner deklariert |
Registry-Fakten
Details aus der Quelldatenbank
| Source Database | Homebrew cask API |
|---|---|
| Tap | homebrew/cask |
| Full Token | amiberry |
| Names |
|
| Depends On | |
| Artifacts | |
| Deprecated | no |
| Disabled | no |
Quellspur
Aus Repository-Daten generiert
Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.
Combined YAML source
View the package source record on GitHub.
Verwendete Quellen
- cross-ecosystem install command graph
- curated configuration and credential file locations
- curated package history
- package relationship graph
- package version freshness
- package-page enrichment