On 08/02/15 18:47, Alexandre Detiste wrote: > Thansk for the files, I only needed to remove the references to doom.wad, > doom2.wad > and nerve.wad; these are already handled by other yaml files.
Some review: +packages: ... + install_to: usr/share/games/dhewm3 I would rather have new games consistently install their data to the default location (/usr/share/games/PACKAGENAME) or some other engine-agnostic location, and use configuration or symlinks in the game engine package (or the game wrapper package like src:quake, where the engine and the game are not a 1:1 match) where necessary to get that data loaded. Remember that the packages produced by game-data-packager are not automatically updated for newer g-d-p versions, so 99% of users will probably build them once and never touch them again. It would be a shame if switching from dhewm3 to some other Doom3 engine (e.g. if iodoom3 becomes a better option in future) broke g-d-p's data packages. In this case I think I would have both D3 and D3:ROE install to usr/share/games/doom3-data, and have D3:BFG install to usr/share/games/doom3-bfg-data. + doom3-data: + debian: + engine: doom3-dhewm3 I would personally have just called the engine package dhewm3 (like the way I packaged ioquake3, iortcw and openjk), but it's up to you. + install_to: usr/share/games/doom3bfg Again, I'd have used doom3-bfg-data here. If the upstream versions of dhewm3 and rbdoom3bfg, or the proprietary Linux binaries from id Software (if any), have default search paths in /usr/share or /usr/local, you can use "try_repack_from:" (see quake3.yaml) to add those to g-d-p's list. That might help to automate the process for some people. Regards, S -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54d89917.2070...@debian.org