On Mon, Oct 29, 2012 at 11:51:07AM +0100, Fabian Greffrath wrote: > since revision 1.33-4, vavoom provides the virtual boom-engine package. > However, it does not supply an alternative for the corresponding binary in > /usr/games/boom. This means, vavoom satisfies freedoom's depends on a boom- > engine, but fails to start it: > > $ freedoom > /usr/games/freedoom: 5: /usr/games/freedoom: /usr/games/boom: not found There are two ways to fix this problem.
The first is to provide an alternative for boom, but 'vavoom' does not support the -iwad flag used by /usr/games/boom, so we would need to write a wrapper. The wrapper would need to convert -iwad /foo/bar/doom2.wad into a mixture of -iwaddir /foo/bar and -doom2. But how can it know that the file doom2.wad is doom2? Do we 1) hardcode a list of basename:game mappings (doom2.wad:doom2; DOOM2.WAD:doom2…) 2) hardcode a list of hashes and compare the arguments Both are quite involved for a simple wrapper and prone to failure if someone modifies their IWAD etc. The second way would be to modify freedoom's wrapper to inspect what is providing 'boom' and switch to using vavoom flags if it detects vavoom. This is also prone to fail, perhaps boom is a custom alternative set by the sysadmin, or points at a binary that we don't recognise. But I think that's probably less likely than the above. > PS: The pkg-games GIT repo is out of sync with the package in unstable! I've fixed this now, thanks for pointing it out. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org