Differences between revisions 122 and 123
Revision 122 as of 2018-09-14 11:05:21
Size: 8571
Editor: ccts
Comment: syntax
Revision 123 as of 2018-09-14 11:41:33
Size: 9173
Editor: ccts
Comment: general informations. Emulators and platforms sections could be developped (which emulator to use for which machine) + distinction of the various available game platforms
Deletions are marked like this. Additions are marked like this.
Line 46: Line 46:
Debian games follow the same logic than other packages with a separation of free, contrib and non-free software. See Debian Policy for an explanation. Debian games availability follow the same logic than other packages with a separation of main, contrib and non-free software. See Debian Policy for an explanation.
Line 52: Line 52:
Do note that not *every* non-free game can be packaged within Debian. Non-free can contain software for which authorization was given to be redistributable, which is not the case for most commercial games. Please do note that not *every* non-free game can be packaged within Debian. Non-free can contain software for which authorization was given to be redistributable, which is not the case for most commercial games.
Line 54: Line 54:
Frequently, some games have a separation between the engine, and the data. It happens some non-free games had their engine rewritten under a free license (i.e: OpenMW), or their source code has been freed (i.e: ioquake3). As a result, some of these engines were packaged and are included into Debian free repositories. Frequently, some games have a separation between the engine, and the data. It happens some commercial games had their engine rewritten under a free license (i.e: OpenMW), or their source code has been freed (i.e: ioquake3). As a result, some of these engines were packaged and are included into Debian main repositories.
Line 60: Line 60:
If a non-free repository exists, why not packaging every game and make it easy?
Do note some non-free games can't go into non-free since they are not redistributable .
The second point brings a little problem however : how game data files can be installed and dealt with? This is where game-data-packager and ./play.it may help.
Line 63: Line 62:
=== GameDataPackager and ./play.it === === game-data-packager and ./play.it ===
Line 65: Line 64:
GameDataPackager and ./play.it are helper tools which exist to answer the question «Where shall I put the data files of a game

If the game you want to play has its engine installed in the repositories, while the game data is not but you own it, some tools provide a way to

Optionally, you may make use of game-data-packager and/or play.it, which purpose is to build a .deb file from the game data you provide. The idea is to provide a clean way to install games, with both engine and data being managed from within your prefered package manager.
game-data-packager is a helper tools which take game data as an input, and build a debian package as the output. The idea is to provide a clean way to install games, with both engine and data being managed from within your prefered package manager.
Line 75: Line 70:
Note: The installed game data packages will appear as "locally installed", this is because such packages can't exist in the tree of our repositories, but still can be installed as independent packages.

./play.it fulfills the same purpose, but extends it to whole games. That means it will package not only the game data, but also the binaries, and create menu entries so that you can start games just like any application from your Desktop Environment.

=== Emulation and implementations ===

There is a vast collection of emulators available in Debian. This ranges from very old computers (such as vice for C64) to console platforms (such as pcsxr for Playstation).

As its name implies, wine is not an emulator. Its purpose is not to virtualize all the hardware, but to translate system calls of Microsoft Windows systems into ones corresponding with the OS running wine.

Useful pages and links :

<<FullSearchCached(category:CategoryGame category:CategoryNotNative language:en)>>

 * https://appdb.winehq.org : compatibility list for applications/games running with wine
 * DebianPackage:playonlinux
Line 78: Line 89:

[[https://lutris.net/|lutris]]

DebianPackage:playonlinux

 * [[https://lutris.net/|lutris]]
 * itch.io
 * Steam
Line 90: Line 98:
=== Not native and emulation ===

<<FullSearchCached(category:CategoryGame category:CategoryNotNative language:en)>>

=== Game Development ===

<<FullSearchCached(category:CategoryGameDevelopment language:en)>>

Translation(s): English - German - Español - Français - Italiano - 日本語 (Nihongo) - Русский - 简体中文

http://www.debian.org/logos/openlogo-nd-50.png http://www.debian.org/Pics/debian.png

Portal/IDB/logo_portal.png Welcome to Debian games portal


Portal/IDB/icon-game-32x32.png This portal is about games, technical knowledge may be required to cheat but isn't mandatory.


Here, we only list:

  • games for which a specific wiki page was created
  • view all option redirects to a list of packages which have been tagged in Debtags database

Adventure view all

Arcadeview all

Boardview all

https://screenshots.debian.net/thumbnail/freedink

https://screenshots.debian.net/thumbnail/fretsonfire

https://screenshots.debian.net/thumbnail/brutalchess

Chess:

Card view all

FPSview all

Multi-User Dungeonview all

https://screenshots.debian.net/thumbnail/aisleriot

https://screenshots.debian.net/thumbnail/openarena

https://screenshots.debian.net/thumbnail/crossfire-client

Platform view all

Puzzleview all

Role-Playing Gameview all

https://screenshots.debian.net/thumbnail/frogatto

https://screenshots.debian.net/thumbnail/enigma

https://screenshots.debian.net/thumbnail/adonthell

Rogue-like:

Simulation view all

Sportview all

Strategyview all

https://screenshots.debian.net/thumbnail/flightgear

https://screenshots.debian.net/thumbnail/supertuxkart

https://screenshots.debian.net/thumbnail/wesnoth

Racing:

Typing view all

Demosview all

Toysview all

Tetris view all

Proprietary

About Games

Debian games availability follow the same logic than other packages with a separation of main, contrib and non-free software. See Debian Policy for an explanation.

Please do note that not *every* non-free game can be packaged within Debian. Non-free can contain software for which authorization was given to be redistributable, which is not the case for most commercial games.

Frequently, some games have a separation between the engine, and the data. It happens some commercial games had their engine rewritten under a free license (i.e: OpenMW), or their source code has been freed (i.e: ioquake3). As a result, some of these engines were packaged and are included into Debian main repositories.

There are two possible scenarios to make use of the engines packaged within Debian free repository :

  • A freely licensed alternative data set exists, and can also be installed within Debian repositories (i.e: freedoom)
  • Using the original game data files, which you may already own or can be obtained by legit ways.

The second point brings a little problem however : how game data files can be installed and dealt with? This is where game-data-packager and ./play.it may help.

game-data-packager and ./play.it

game-data-packager is a helper tools which take game data as an input, and build a debian package as the output. The idea is to provide a clean way to install games, with both engine and data being managed from within your prefered package manager.

More infos :

Note: The installed game data packages will appear as "locally installed", this is because such packages can't exist in the tree of our repositories, but still can be installed as independent packages.

./play.it fulfills the same purpose, but extends it to whole games. That means it will package not only the game data, but also the binaries, and create menu entries so that you can start games just like any application from your Desktop Environment.

Emulation and implementations

There is a vast collection of emulators available in Debian. This ranges from very old computers (such as vice for C64) to console platforms (such as pcsxr for Playstation).

As its name implies, wine is not an emulator. Its purpose is not to virtualize all the hardware, but to translate system calls of Microsoft Windows systems into ones corresponding with the OS running wine.

Useful pages and links :

Platforms