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=<release> <scenarios> 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/<scenario> 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
