Bug#119911: ITP: alephone - marathon engine for data games
Le lundi 7 décembre 2015, 16:23:31 PICCORO McKAY Lenz a écrit :
> HEre are preliminary dsc sources for alephone engine
>
> the game-data-packager has git entries for data (please are SCENARIOS) games
>
> Alexander Detiste added a rule in G-D-P for Marthon, but that rule are
> too basic and lack of many missing necesary files
>
> http://anonscm.debian.org/cgit/pkg-games/game-data-packager.git/commit/?id=276b4a06fb63b85be1db5069f0bc80620a1bc79e
I made these GDP package as dumb pas possible on purpose:
The way to go is also explained here in GDP code, quoting Simon in full.
http://anonscm.debian.org/cgit/pkg-games/game-data-packager.git/tree/game_data_packager/games/doom_common.py
Please do not follow this example for newly-supported games other than
the Doom family (Doom, Heretic, Hexen, Strife, Hacx, Chex Quest).
For new games it is probably better to use game-data-packager to ship only
the non-distributable files, and ship DFSG files (such as icons
and .desktop files) somewhere else.
One way is to have the engine package contain the wrapper scripts,
.desktop files etc. (e.g. src:openjk, src:iortcw). This is the simplest
thing if the engine is unlikely to be used for other games and alternative
engine versions are unlikely to be packaged.
Another approach is to have a package for the engine (like src:ioquake3)
and a package for the user-visible game (like src:quake, containing
wrapper scripts, .desktop files etc.). This is more flexible if the engine
can be used for other user-visible games (e.g. OpenArena, Nexuiz Classic)
or there could reasonably be multiple packaged engines (e.g. Quakespasm,
Darkplaces).
> game-data-packager produce with the engine, inside scenarios packages
> 3 .desktop files with a TryExec clause
> that point to a file provided by G-D-P -created, .deb
> for example /usr/share/games/marathon-{1|2|3}/try-exec
> but those are currently symlinks back to /usr/games/alephone , that
> are enought only for determine if can be lauched but NOT FOR lauch
> each game!
The TryExec and Exec aren't the same thing of course.
If you provide a .desktop file for each episode,
then each can call the engine directly without needing a wrapper script.
Reply to: