Tobias,
Thanks, the only bit still missing in doom3.yaml is the size (in
bytes) of the .pk4 files.
The output of "cksums" is ok too.
---
>> (Simon)
>> Again, I'd have used doom3-bfg-data here.
I think it's better to have two distinct doom3-{*-}data and
doom3bfg-{*-}data namespaces,
so we immediately see if an expansion is for the original game or the
BFG edition.
So doom3bfg-data instead of doom3-bfg-data,
with default install_to = /usr/share/games/doom3bfg
doom3-bfg-data makes it feels like it were an expansion for doom3-data
> (Tobias)
> Game's default search patch is /usr/share/games/doom3bfg.
This is perfect
>> Thanks 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.
>
> note sure what's the effect... but the bfg edition includes those games
> as well, so they also need to be installed.
The current yaml layout only accept 1 steam id+path to look into for files;
so someone would have now to do:
game-data-packager doom3
game-data-packager doom2 <full path of Doom 3 BFG>
game-data-packager doom <full path of Doom 3 BFG>
to package everything, not much fun.
I'm working on alternative G-D-P frontend that can
"package all my supported steam games" or
"package all my supported steam games not yet packaged";
and Simon has plans for a GUI too.
Simon,
I guess adding "steam2:" would be too hackish for the yaml...
So we need to move everything to a new layout like this, ok ?
(I can make the populate...() accept both syntax too):
packages:
doom2-wad:
steam:
2300: common/Doom 2
208200: common/DOOM 3 BFG Edition
Alexandre
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
