Ubuntu
chocolate-doom package

chocolate-doom 2.2.1-1 source package in Ubuntu

Changelog

chocolate-doom (2.2.1-1) unstable; urgency=medium

  * Imported Upstream version 2.2.1
  * Install upstream appdata files and remove them in the clean rule.
  * Provide unique license names in debian/copyright.

 -- Fabian Greffrath <email address hidden>  Fri, 18 Sep 2015 09:47:59 +0200

Upload details

Uploaded by:
Debian Games Group
Uploaded to:
Sid
Original maintainer:
Debian Games Group
Architectures:
any
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
chocolate-doom_2.2.1-1.dsc 2.4 KiB 929c80d72261c46da12d00079f18d7d688348a5c555081aee7fc2b470f70baed
chocolate-doom_2.2.1.orig.tar.gz 1.8 MiB aa924052f3cadc4f0a8b8b92c69d134f9ca4d35add1b0a86bf9e04b6c1b71d90
chocolate-doom_2.2.1-1.debian.tar.xz 11.9 KiB caba725669875df0dd6dce398442e27d03722d60a3769a20c0ab45478ba29621

Available diffs

No changes file available.

Binary packages built by this source

chocolate-common: Common files for Chocolate Doom/Heretic/Hexen/Strife

 Chocolate Doom aims to accurately reproduce the original DOS version of
 Doom and other games based on the Doom engine in a form that can be
 run on modern computers. Unlike most modern Doom engines, Chocolate Doom
 is not derived from the Boom source port and does not inherit its
 features (or bugs).
 .
 Originally, Chocolate Doom was only a Doom source port. The project
 now includes ports of Heretic and Hexen, and Strife.
 .
 This package contains the dedicated server for multiplayer games and
 the common configuration tool for all four ports.

chocolate-common-dbgsym: debug symbols for package chocolate-common

 Chocolate Doom aims to accurately reproduce the original DOS version of
 Doom and other games based on the Doom engine in a form that can be
 run on modern computers. Unlike most modern Doom engines, Chocolate Doom
 is not derived from the Boom source port and does not inherit its
 features (or bugs).
 .
 Originally, Chocolate Doom was only a Doom source port. The project
 now includes ports of Heretic and Hexen, and Strife.
 .
 This package contains the dedicated server for multiplayer games and
 the common configuration tool for all four ports.

chocolate-doom: Doom engine closely-compatible with Vanilla Doom

 Chocolate Doom aims to accurately reproduce the original DOS version of
 Doom and other games based on the Doom engine in a form that can be
 run on modern computers. Unlike most modern Doom engines, Chocolate Doom
 is not derived from the Boom source port and does not inherit its
 features (or bugs).
 .
 Chocolate Doom is a port of Id Software's 1993 game "Doom" that is designed
 to behave as similar to the original DOS version of Doom as is possible.
 .
 Chocolate Doom requires game data to play. Free game data is available in the
 freedm package. Commercial game data can be packaged using
 "game-data-packager". Chocolate Doom supports all flavors of Doom, including
 The Ultimate Doom, Doom 2 and Final Doom as well as Chex(R) Quest, HACX and
 FreeDM.

chocolate-doom-dbgsym: debug symbols for package chocolate-doom

 Chocolate Doom aims to accurately reproduce the original DOS version of
 Doom and other games based on the Doom engine in a form that can be
 run on modern computers. Unlike most modern Doom engines, Chocolate Doom
 is not derived from the Boom source port and does not inherit its
 features (or bugs).
 .
 Chocolate Doom is a port of Id Software's 1993 game "Doom" that is designed
 to behave as similar to the original DOS version of Doom as is possible.
 .
 Chocolate Doom requires game data to play. Free game data is available in the
 freedm package. Commercial game data can be packaged using
 "game-data-packager". Chocolate Doom supports all flavors of Doom, including
 The Ultimate Doom, Doom 2 and Final Doom as well as Chex(R) Quest, HACX and
 FreeDM.

chocolate-heretic: Heretic engine closely-compatible with Vanilla Heretic

 Chocolate Doom aims to accurately reproduce the original DOS version of
 Doom and other games based on the Doom engine in a form that can be
 run on modern computers. Unlike most modern Doom engines, Chocolate Doom
 is not derived from the Boom source port and does not inherit its
 features (or bugs).
 .
 Chocolate Heretic is a port of Raven Software's 1994 game "Heretic" that
 aims to behave as similar to the original DOS version of Heretic as possible.
 .
 Chocolate Heretic requires game data to play. Commercial game data can be
 packaged using "game-data-packager".

chocolate-heretic-dbgsym: debug symbols for package chocolate-heretic

 Chocolate Doom aims to accurately reproduce the original DOS version of
 Doom and other games based on the Doom engine in a form that can be
 run on modern computers. Unlike most modern Doom engines, Chocolate Doom
 is not derived from the Boom source port and does not inherit its
 features (or bugs).
 .
 Chocolate Heretic is a port of Raven Software's 1994 game "Heretic" that
 aims to behave as similar to the original DOS version of Heretic as possible.
 .
 Chocolate Heretic requires game data to play. Commercial game data can be
 packaged using "game-data-packager".

chocolate-hexen: Hexen engine closely-compatible with Vanilla Hexen

 Chocolate Doom aims to accurately reproduce the original DOS version of
 Doom and other games based on the Doom engine in a form that can be
 run on modern computers. Unlike most modern Doom engines, Chocolate Doom
 is not derived from the Boom source port and does not inherit its
 features (or bugs).
 .
 Chocolate Hexen is a port of Raven Software's 1995 game "Hexen" that aims
 to behave as similar to the original DOS version of Hexen as possible.
 .
 Chocolate Hexen requires game data to play. Commercial game data can be
 packaged using "game-data-packager".

chocolate-hexen-dbgsym: debug symbols for package chocolate-hexen

 Chocolate Doom aims to accurately reproduce the original DOS version of
 Doom and other games based on the Doom engine in a form that can be
 run on modern computers. Unlike most modern Doom engines, Chocolate Doom
 is not derived from the Boom source port and does not inherit its
 features (or bugs).
 .
 Chocolate Hexen is a port of Raven Software's 1995 game "Hexen" that aims
 to behave as similar to the original DOS version of Hexen as possible.
 .
 Chocolate Hexen requires game data to play. Commercial game data can be
 packaged using "game-data-packager".

chocolate-strife: Strife engine closely-compatible with Vanilla Strife

 Chocolate Doom aims to accurately reproduce the original DOS version of
 Doom and other games based on the Doom engine in a form that can be
 run on modern computers. Unlike most modern Doom engines, Chocolate Doom
 is not derived from the Boom source port and does not inherit its
 features (or bugs).
 .
 Chocolate Strife is an accurate and complete recreation of Rogue
 Entertainment's "Strife: Quest for the Sigil". It was created through more
 than two years of reverse engineering effort with the blessings of the
 original programmers of the game.
 .
 Chocolate Strife requires game data to play. Commercial game data can be
 packaged using "game-data-packager".

chocolate-strife-dbgsym: debug symbols for package chocolate-strife

 Chocolate Doom aims to accurately reproduce the original DOS version of
 Doom and other games based on the Doom engine in a form that can be
 run on modern computers. Unlike most modern Doom engines, Chocolate Doom
 is not derived from the Boom source port and does not inherit its
 features (or bugs).
 .
 Chocolate Strife is an accurate and complete recreation of Rogue
 Entertainment's "Strife: Quest for the Sigil". It was created through more
 than two years of reverse engineering effort with the blessings of the
 original programmers of the game.
 .
 Chocolate Strife requires game data to play. Commercial game data can be
 packaged using "game-data-packager".