macOS
Homebrewverifiziert · 100%
brew install crispy-doomlocal Homebrew formula metadata
MacPortsverifiziert · 94%
sudo port install crispy-doomMacPorts ports tree · games/crispy-doom/Portfile · Quelle: api.github.com
brew
crispy-doom mit Homebrew, apk, apt, MacPorts, Nix, zypper installieren
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für crispy-doom in AI-Agent-Workflows.
Installation
Weitere Installationsbefehle
Linux
Alpine Linux apkverifiziert · 92%
sudo apk add crispy-doomAlpine Linux edge package indexes · crispy-doom · Quelle: dl-cdn.alpinelinux.org
Debian aptverifiziert · 92%
sudo apt install crispy-doomDebian stable package indexes · crispy-doom · Quelle: deb.debian.org
Nixverifiziert · 92%
nix profile install nixpkgs#crispy-doomnixpkgs package indexes · pkgs/by-name/cr/crispy-doom/package.nix · Quelle: api.github.com
openSUSE zypperverifiziert · 92%
sudo zypper install crispy-doomopenSUSE Tumbleweed package metadata · crispy-doom · Quelle: download.opensuse.org
Überblick
Paketzusammenfassung
Limit-removing enhanced-resolution Doom source port based on Chocolate Doom
Projektlinks
Befehle und Aliase
- crispy-doom
- crispy-doom-setup
- crispy-heretic
- crispy-heretic-setup
- crispy-hexen
- crispy-hexen-setup
- crispy-server
- crispy-strife
- crispy-strife-setup
Verlauf
Projektgeschichte und Nutzung
Crispy Doom is a Doom source port that sits between strict vanilla compatibility and modern convenience. It is a friendly fork of Chocolate Doom with higher resolution, raised engine limits, and optional gameplay and visual enhancements while preserving compatibility goals that matter to demo, savegame, and netplay users.
Projektgeschichte
The project was created by Fabian Greffrath in 2014 and explicitly traces its origin to Chocolate Doom. The README says the name refers both to its crisp 640x400 internal resolution and to its origin, and the legal section marks Crispy Doom's additional copyright from 2014 onward.
Crispy Doom's design brief is conservative by source-port standards: it aims at faithful Doom play, supports limit-removing vanilla maps, and avoids Boom or ZDoom map formats while adding optional quality-of-life features. This makes it attractive to users who want a packaged executable with enhancements but not a fundamentally different engine family.
Adoptionsgeschichte
Official download instructions list Windows release binaries, MacPorts and Homebrew on macOS, and Debian/Ubuntu packages from Debian 10 and Ubuntu 19.10 onward. That distribution footprint is important for a source port because users often want the engine packaged separately from commercial or shareware IWAD data.
Wie es verwendet wird
Users run Crispy Doom to play Doom-family IWADs and compatible PWADs with enhanced resolution, widescreen rendering, uncapped framerate, raised static limits, and optional features enabled through the Crispness menu, setup tools, or command-line parameters.
Warum Paket-Nerds sich dafür interessieren
Crispy Doom is package-manager friendly because it keeps the engine open source and separate from game data, exposes multiple binaries for Doom-engine relatives, and documents compatibility boundaries clearly. For retro-gaming packages, those boundaries help maintainers set expectations about IWAD ownership, save/demo compatibility, and supported mod formats.
Zeitleiste
- 2014: Repository created and project copyright begins.
- 2018: Crispy Doom 5.4 release published on GitHub releases.
- 2019: Debian/Ubuntu-era packaging is reflected in the official install notes for Debian 10 and Ubuntu 19.10 or later.
Related projects
- Chocolate Doom is the upstream fork base and compatibility reference.
- Doom Retro, MBF, and WinMBF are acknowledged as influences or debugging references in the README.
- Freedoom and the Doom shareware WAD are documented data options for users who do not own commercial IWADs.
Quellen
Sicherheitslage
Risikostufe: blue
broad file, network, media, or database tool signal.
Risikoklassifikator
blue Risiko · mittel Konfidenz · tool
Warum
- broad file, network, media, or database tool signal
Signale
- text:server
Installationsverhalten
- In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
- Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
- Installiert mit 6 Laufzeitabhängigkeiten.
- Build-Metadaten listen 3 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.
Executables
Installierte Executables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
crispy-doom | cli | globales Executable | |
crispy-doom-setup | cli | globales Executable | |
crispy-heretic | cli | globales Executable | |
crispy-heretic-setup | cli | globales Executable | |
crispy-hexen | cli | globales Executable | |
crispy-hexen-setup | cli | globales Executable | |
crispy-server | cli | globales Executable | |
crispy-strife | cli | globales Executable | |
crispy-strife-setup | 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-25
Manager-Version7.1
Manager aktualisiert2026-06-18
lokale DatenOK
Upstreamaktuell
neueste erkannte Versioncrispy-doom-7.1
https://github.com/fabiangreffrath/crispy-doom
- OKEs wurden keine Aktualitätswarnungen generiert.
Installationsmetadaten
Paketmetadaten
| Paketschlüssel | brew:crispy-doom |
|---|---|
| Version | 7.1 |
| Paketmanager | Homebrew |
| Paketmanager-Seite | https://formulae.brew.sh/formula/crispy-doom |
| Homepage | https://github.com/fabiangreffrath/crispy-doom |
| Repository | https://github.com/fabiangreffrath/crispy-doom |
| Upstream-Dokumentation | https://github.com/fabiangreffrath/crispy-doom#readme |
| Lizenz | GPL-2.0-or-later |
| Quellarchiv | https://github.com/fabiangreffrath/crispy-doom/archive/refs/tags/crispy-doom-7.1.tar.gz |
| Zuletzt aktualisiert | 2026-06-18T02:28:56-04:00 |
| Pulse | updated |
| Abhängigkeiten | fluid-synth, libpng, libsamplerate, sdl2-compat, sdl2_mixer, sdl2_net |
| Build-Abhängigkeiten | autoconf, automake, pkgconf |
| 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 | crispy-doom |
| 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 |
|
Source-Datenbank-Treffer
Andere Paketmanager-Einträge
Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.
Debian apt95%
crispy-doom 7.0-1
Limit-raising medium-resolution Doom engine based on Chocolate Doom
https://fabiangreffrath.github.io/crispy-homepage
sudo apt install crispy-doom- Section: games
- Architecture: amd64
- 8 Abhängigkeiten
- 4 stellt bereit
- 2 optionale Abhängigkeiten
- normalized package name match
- Abgeglichen nach: Crispy Doom
Nix95%
crispy-doom
nix profile install nixpkgs#crispy-doom- normalized package name match
- Abgeglichen nach: Crispy Doom
Ubuntu apt95%
crispy-doom 6.0-2build2
Limit-raising medium-resolution Doom engine based on Chocolate Doom
sudo apt install crispy-doom- Section: universe/games
- Architecture: amd64
- 8 Abhängigkeiten
- 4 stellt bereit
- 2 optionale Abhängigkeiten
- normalized package name match
- Abgeglichen nach: Crispy Doom
apk95%
crispy-doom 7.1-r0
Limit-removing enhanced-resolution Doom source port based on Chocolate Doom
https://github.com/fabiangreffrath/crispy-doom
sudo apk add crispy-doom- License: GPL-2.0-or-later
- Architecture: x86_64
- Source Package: crispy-doom
- 1 Abhängigkeiten
- 1 stellt bereit
- normalized package name match
- Abgeglichen nach: Crispy Doom
apk95%
crispy-doom-doc 7.1-r0
Limit-removing enhanced-resolution Doom source port based on Chocolate Doom (documentation)
https://github.com/fabiangreffrath/crispy-doom
sudo apk add crispy-doom-doc- License: GPL-2.0-or-later
- Architecture: x86_64
- Source Package: crispy-doom
- normalized package name match
- Abgeglichen nach: Crispy Doom
zypper95%
crispy-doom 7.1-1.4
Higher resolution DOOM/Heretic/Hexen/Strife source port
https://github.com/fabiangreffrath/crispy-doom
sudo zypper install crispy-doom- License: GPL-2.0-or-later
- Category: Amusements/Games/3D/Shoot
- Architecture: x86_64
- Source Package: crispy-doom
- 10 Abhängigkeiten
- 6 stellt bereit
- normalized package name match
- Abgeglichen nach: Crispy Doom
zypper95%
crispy-doom-bash-completion 7.1-1.4
Crispy Doom command line completion support for bash
https://github.com/fabiangreffrath/crispy-doom
sudo zypper install crispy-doom-bash-completion- License: GPL-2.0-or-later
- Category: System/Shells
- Architecture: noarch
- Source Package: crispy-doom
- 1 stellt bereit
- normalized package name match
- Abgeglichen nach: Crispy Doom
MacPorts95%
crispy-doom
sudo port install crispy-doom- normalized package name match
- Abgeglichen nach: Crispy Doom
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
- Geiger risk classifier
- Nucleus package database
- av.db category and tag curation
- cross-ecosystem install command graph
- curated package history
- external package-manager database matches
- package relationship graph
- package version freshness
- package-page enrichment