Bug#119911: ITP: alephone - marathon engine for data games
2015-12-08 1:33 GMT-04:30 Alexandre Detiste : > I don't think anyone else will come up with an alternative marathon engine > anyday. Yes, that its! > So please: one alephone source package that builds one alephone binary package > that includes three .desktop files (for a starter, the extra levels can be > added later) > and the launcher if needed. alephone source and the resulting alephone package now has those: * /usr/games/alephone (engine itselft) * /usr/share/games/alephone/alephone-laucher (bash script to suymlink on each scenario package) and its respective manpages BUT: > GDP will not provide things like the one provided by src:quake, as there's > no way to update these after the local GDP package has been manually built. if that its, so source engine will also made 3 packges (marathon/1/2/3) that ship those files and depends of the packages provides by GDP? this mean the alephone source must produce : * marathon * marathon2 * marathon3 these packages will handle desktop files, desktop icons, root debian menu entries and laucher symlink and as seem you point, will depends of the data packages produced by GDP right? please confirme for made the proper changes and send to you the dsc files with all need!
Bug#119911: ITP: alephone - marathon engine for data games
I don't think anyone else will come up with an alternative marathon engine anyday. So please: one alephone source package that builds one alephone binary package that includes three .desktop files (for a starter, the extra levels can be added later) and the launcher if needed. Keep it simple. Please no virtual packages like for quake, better follow iortcw as an example. GDP will not provide things like the one provided by src:quake, as there's no way to update these after the local GDP package has been manually built. Greets, Alexandre
Bug#119911: ITP: alephone - marathon engine for data games
ok lest take in consideration u'r notes: 2015-12-07 17:24 GMT-04:30, Alexandre Detiste : > 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
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.
Bug#119911: ITP: alephone - marathon engine for data games
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
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!
Thats are not enought to made work each scenario, due each scenario
are independent data game and works without any other data, its not
same as other engines & data's that need original files for work
Each scenario to work need that be parsed as LAST argument to the
engine, this avoid modification of the environment using the
ALEPHONE_DATA variable
the script that i provide solves that: see the already provide manpage
for usage, just symlink each lauch tho the script and that all, can be
included in the engine package but i prefer a common package produced
by game-data-packager or something like quake does (a meta empty that
depends/recommends both data and engine)
the dsc sources that i provide has inside all the necesary to promote
the engine package
PLEASE NOTE THAT MENTORS HAVE A PROBLEM WITH KEY GPG VALIDATION AND I
MAIL IN TWO OPORTUNITIES WITH OUT ANY REPLY ABOUT!
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
marathon-laucher.sh
Description: Bourne shell script
marathon-laucher.sh
Description: Bourne shell script
marathon-launcher.6
Description: Binary data
alephone_20150620-0.dsc
Description: Binary data
alephone_20150620-0.debian.tar.xz
Description: application/xz
Bug#119911: ITP: alephone - marathon engine for data games
i thinks there's some missing points, engine will lauch directly those
SCENARIOS directly?, correct me if i dont understand those points:
2015-11-28 12:42 GMT-04:30, Alexandre Detiste :
> The package with the engine should also provide 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
> as symlinks back to /usr/games/alephone .
asmlinks to the engine without any directory data direction does not
start the game,
that's why i provide one of the two scripts.. the marathonlaucher.sh
also the scenarios (please PLEASE does not named "-data", use
"-scenarios") must goes into a global "marathon" directory under
/usr/share/games
> The engine should go in contrib, as the assets are not DFSG-free and
> the engine is useless without assets.
the engine can go to main as with darkplaces and quakespasm does
take in consideration if u dont are played the game before... and dont
understand the working of the engine..
a extra package as quake over quake-data packages, by example, can
hadle that extra script, the script are based in previous work of this
issue, and on the quake relationship packages
--
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Bug#119911: ITP: alephone - marathon engine for data games
Hi,
I've added a rule in G-D-P for Marthon.
http://anonscm.debian.org/cgit/pkg-games/game-data-packager.git/commit/?id=276b4a06fb63b85be1db5069f0bc80620a1bc79e
The package with the engine should also provide 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
as symlinks back to /usr/games/alephone .
This way the icons are only displayed if the matching data are installed.
The engine should go in contrib, as the assets are not DFSG-free and
the engine is useless without assets.
>3) the game-data-packager that that preliminary installer
>"marathoninstaller.sh" with release date as argument and scenario as
>second argument
Hum, there's built-in support for that, this shell script is not needed.
Alexandre Detiste
Bug#119911: ITP: alephone - marathon engine for data games
user pkg-games-de...@lists.alioth.debian.org tag games 119911 forcemerge 85673 119911 hi mantainers, i take some work over alephon and marathon related i made two scripts, one to downloading and help game-data-packager supports marathon trilogy and other to lauch using one only script that detects any futher data based on the previous insaller the behavior are: 1) package alephone can go to main due only provided "engine", just like some others does 2) game-data-packager will support data for engine packages, but each packaged data game will provide own laucher and menu entries 3) the game-data-packager that that preliminary installer "marathoninstaller.sh" with release date as argument and scenario as second argument 3.1) the invocation installer: marathoninstaller install= 3.2) installer will download from oficial github alephone the data files NOTE: data files for alephone from oficial marathon trilogy does not work! 3.3) installer will unzip and put in debian tmp, (for game-data-packager change that obviously) 4) laucher script will expected data scenarios will be n /usr/share/games/marathon/ 4.1) each scenario works independient from another, including those unnoficial or made 4.2) script selft detects own name invocation an lauch respective game example for marathon 2 durandal: marathoninstaller.sh install=20150620 marathon-2 the engine package "alephone" can provide the script named attached here "marathonlaucher.sh" or we can made a main marathon package tha provide the laucher and if laucher does not fond data, help users what must install or notify something installer will download from github oficial repository from release 20150620 the file Marathon2-20150620-Data.zip, the unzip in "file/Marathon 2", due this have a space in path will rename to "marathon2" and then put into debian/tmp, file names inside data dir scenario must remain unhanged ... game-data-packager if se that preliminary script must put files under /usr/share/games/marathon with own directory as "marathon2" and each scenario package must symlink real script (named attached here as marathonlaucher.sh), in this case "marathon-2" (/usr/games/marathon-2 -> /usr/games/marathon", and provided respective menu entries laucher spected found scenario in /usr/share/games/marathon/marathon-2, will detect if laucher itself was "marathon-2" or "marathon2" trhought symlink to real laucher script, and set directory scenario gam data, then lauch IMPORTANT: due not all GPL mesa modules today provide OpenGL (well all modules fails to provide, only intel does) the script automatically detect if opengl support are present and disable it before lauch the proper game -- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com marathoninstaller.sh Description: Bourne shell script marathonlauncher.sh Description: Bourne shell script
Bug#119911: ITP: alephone - marathon engine for data games
retitle 119911 ITP: alephone -- marathon engine for related data games owner 119911 ! thanks i want to take on this issue i have a alephone package with those changes to able to upload to main.. if we take in consideration the work on quake related ackages we can take: a) a alephone engine package in main that provides only engine software b) a marathon game package that ship in same way the engine and adata as quake does c) a excalibur morganas's revenge contrib package that can provide marathon-data d) a marathon-data packages entries in game-data-packager as MUST BE any feedbafck please?
