# Installer crispy-doom avec Homebrew, apk, apt, MacPorts, Nix, zypper

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de crispy-doom pour les workflows d'agents IA.

## installation

```sh
sudo av install brew:crispy-doom
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install crispy-doom
```

  Preuve: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install crispy-doom
```

  Preuve: MacPorts ports tree: games/crispy-doom/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

### Linux

- apk (92%):

```sh
sudo apk add crispy-doom
```

  Preuve: Alpine Linux edge package indexes: crispy-doom from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz

- Debian apt (92%):

```sh
sudo apt install crispy-doom
```

  Preuve: Debian stable package indexes: crispy-doom from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz

- Nix (92%):

```sh
nix profile install nixpkgs#crispy-doom
```

  Preuve: nixpkgs package indexes: pkgs/by-name/cr/crispy-doom/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

- zypper (92%):

```sh
sudo zypper install crispy-doom
```

  Preuve: openSUSE Tumbleweed package metadata: crispy-doom from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst

## Faits du paquet

- **Clé du paquet:** brew:crispy-doom
- **Gestionnaire de paquets:** Homebrew
- **Version:** 7.1
- **Résumé source:** Limit-removing enhanced-resolution Doom source port based on Chocolate Doom
- **Page d'accueil:** <https://github.com/fabiangreffrath/crispy-doom>
- **Dépôt:** <https://github.com/fabiangreffrath/crispy-doom>
- **Dernière mise à jour:** 2026-06-18T02:28:56-04:00
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- crispy-doom (alias)
- crispy-doom-setup (alias)
- crispy-heretic (alias)
- crispy-heretic-setup (alias)
- crispy-hexen (alias)
- crispy-hexen-setup (alias)
- crispy-server (alias)
- crispy-strife (alias)
- crispy-strife-setup (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 7.1
## Historique du projet et usages

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.

### Historique du projet

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.

### Historique d'adoption

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.

### Modes d'utilisation

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.

### Pourquoi les passionnés de paquets s'y intéressent

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.

### Chronologie

- 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.

### Sources

- <https://github.com/fabiangreffrath/crispy-doom#readme>
- <https://github.com/fabiangreffrath/crispy-doom/wiki>
- <https://github.com/fabiangreffrath/crispy-doom/releases/tag/crispy-doom-5.4>


## Notes de sécurité

broad file, network, media, or database tool signal.

- **Risque Geiger:** blue / moyen
- broad file, network, media, or database tool signal

## Autres enregistrements de gestionnaires de paquets

- Debian apt - crispy-doom - 7.0-1: normalized package name match | Debian stable package indexes: crispy-doom from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | Limit-raising medium-resolution Doom engine based on Chocolate Doom | https://fabiangreffrath.github.io/crispy-homepage
- Nix - crispy-doom: normalized package name match | nixpkgs package indexes: pkgs/by-name/cr/crispy-doom/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- Ubuntu apt - crispy-doom - 6.0-2build2: normalized package name match | Ubuntu 24.04 LTS package indexes: crispy-doom from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | Limit-raising medium-resolution Doom engine based on Chocolate Doom | https://crispy-doom.org/
- apk - crispy-doom - 7.1-r0: normalized package name match | Alpine Linux edge package indexes: crispy-doom from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz | Limit-removing enhanced-resolution Doom source port based on Chocolate Doom | https://github.com/fabiangreffrath/crispy-doom
- apk - crispy-doom-doc - 7.1-r0: normalized package name match | Alpine Linux edge package indexes: crispy-doom-doc from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz | Limit-removing enhanced-resolution Doom source port based on Chocolate Doom (documentation) | https://github.com/fabiangreffrath/crispy-doom
- zypper - crispy-doom - 7.1-1.6: normalized package name match | openSUSE Tumbleweed package metadata: crispy-doom from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Higher resolution DOOM/Heretic/Hexen/Strife source port | https://github.com/fabiangreffrath/crispy-doom
- zypper - crispy-doom-bash-completion - 7.1-1.6: normalized package name match | openSUSE Tumbleweed package metadata: crispy-doom-bash-completion from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Crispy Doom command line completion support for bash | https://github.com/fabiangreffrath/crispy-doom
- MacPorts - crispy-doom: normalized package name match | MacPorts ports tree: games/crispy-doom/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/crispy-doom.yml](https://github.com/mxcl/pkgdb/blob/main/combined/crispy-doom.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph
