Installer open-tyrian avec Homebrew, apt, Nix, zypper

Liens du projet

• Page d'accueil
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• opentyrian

Historique du projet

OpenTyrian's project documentation says Jason Emery gave the OpenTyrian developers a copy of the Tyrian 2.1 source code, which was ported from Turbo Pascal to C. The project's FAQ clarifies the distinction: Tyrian itself is not open source, but the OpenTyrian rewrite is open source and was licensed to the port developers for that purpose.

The port replaced DOS-specific code with SDL, which made the game practical to build and run across desktop and hobbyist platforms. The GitHub README describes the project as an open-source port of the DOS game and notes that the freeware Tyrian 2.1 data files are still required.

Historique d'adoption

OpenTyrian spread through game-source-port communities, Linux distributions, package managers, and console/homebrew builds because it preserved a well-liked DOS shooter in a form that could compile on modern systems. The GitHub wiki lists Windows releases and community builds for platforms including Android, Amiga, Dreamcast, DS, GameCube, GP2X, PSP, Wii, and others.

The Homebrew formula, Debian/Ubuntu packages, Nix package, and Flathub entry reflect its role as a small but durable open-source game port: users install the engine, then supply or download the freeware Tyrian 2.1 data files.

Modes d'utilisation

Players run opentyrian to play Tyrian's story mode, one- or two-player arcade modes, and networked multiplayer. The README documents keyboard controls, fullscreen toggling, sidekick firing, and manual command-line setup for network play.

Packagers and porters treat OpenTyrian like an SDL game engine with separate data. That split matters: the executable can be GPL-licensed and packaged, while the data files come from the freeware Tyrian 2.1 release rather than from the source tree.

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

OpenTyrian is package-nerd significant because it is a clean example of the engine/data split common to open-source ports of commercial games. The package manager can distribute the source port, but runtime usefulness depends on finding compatible game data.

It also shows how small game ports survive through build portability. Moving from Turbo Pascal and x86 assembly to C plus SDL turned a DOS-era game into something package managers and hobbyist platforms could keep alive.

Chronologie

• 1995: Tyrian was released for MS-DOS by Eclipse Software and Epic MegaGames, according to later game-history references.
• 2004-08: OpenTyrian's FAQ says Tyrian was released as freeware by Jason Emery.
• 2007: project histories and game-history references describe the Tyrian source handoff and the OpenTyrian rewrite effort.
• 2013-09-07: the OpenTyrian wiki references a 2.1.20130907 release in its historical downloads context.
• 2022-11-24: the GitHub repository lists v2.1.20221123 as a release dated 2022-11-24.

Related projects

• Tyrian 2.1 is the required data-file target for OpenTyrian.
• SDL and SDL_net are the portability layers behind the modern C port.
• OpenTyrian2000 is a related fork aimed at Tyrian 2000-era content, according to community project histories.

Sources

• https://en.wikipedia.org/wiki/Tyrian_(video_game)
• https://flathub.org/en/apps/com.github.opentyrian.OpenTyrian
• https://formulae.brew.sh/formula/open-tyrian
• https://github.com/opentyrian/opentyrian
• https://github.com/opentyrian/opentyrian/wiki
• https://github.com/opentyrian/opentyrian/wiki/FAQ