ok lest take in consideration u'r notes: 2015-12-07 17:24 GMT-04:30, Alexandre Detiste <alexandre.deti...@gmail.com>: > 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. its the way proposed also in the second suggestion: > > 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. currently alephone only works for marathon related games, so there's no other game derived! but the secon approach also can be applied due the wrapper script can be put in those kind of package: > > 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). > > If you provide a .desktop file for each episode, > then each can call the engine directly without needing a wrapper script. > i can provide it, inclusivelly i already doit! but firts we must decided how we made the scenarios packages! or what will be included in the engine package, do u take a review on the files i provided? or something!?
-- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
