Bug#691741: Provides: boom-engine, but does not supply /usr/games/boom

2012-11-13 Thread Jon Dowland
On Mon, Nov 12, 2012 at 11:18:14AM +0100, Fabian Greffrath wrote: > I have taken the liberty to fix this myself in GIT master. The > vavoom executable now registeres itself as an alternative for doom > and boom and works perfectly with the freedoom wrapper script. > Furthermore, I have fixed what I

Bug#691741: Provides: boom-engine, but does not supply /usr/games/boom

2012-11-12 Thread Fabian Greffrath
Am 09.11.2012 14:07, schrieb Fabian Greffrath: Erm, we can have all of this without any source code changes if we just changed the -iwaddir parameter in the /u/g/vavoom wrapper script to read "-iwaddir . / /usr/share/games/doom/", i.e. we merely add "." and "/" to take care of relative and absolu

Bug#691741: Provides: boom-engine, but does not supply /usr/games/boom

2012-11-09 Thread Fabian Greffrath
Am 09.11.2012 09:37, schrieb Fabian Greffrath: That way, if you have a doom.wad in your current directory and type "vavoom -iwad doom.wad" it will take this file. If the file is absent, then it will take the one from the next directory in the iwaddirs array, i.e. typically /u/s/g/d/doom.wad. Thus

Bug#691741: Provides: boom-engine, but does not supply /usr/games/boom

2012-11-09 Thread Fabian Greffrath
Am 08.11.2012 14:41, schrieb Fabian Greffrath: the string just as before. However, this may confuse users who want to pass the file name of an iwad in the current directory or in a directory relative to it. But changing this would break the current (though undocumented) behaviour, so I am not sur

Bug#691741: Provides: boom-engine, but does not supply /usr/games/boom

2012-11-08 Thread Fabian Greffrath
Am 07.11.2012 09:40, schrieb Jon Dowland: 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. Actually, vavoom *does* have this flag, c.f. source/file.cpp:492. It is just not documented anyw

Bug#691741: Provides: boom-engine, but does not supply /usr/games/boom

2012-11-07 Thread Jon Dowland
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- > en

Bug#691741: Provides: boom-engine, but does not supply /usr/games/boom

2012-10-29 Thread Fabian Greffrath
Package: vavoom Version: 1.33-4 Severity: normal Hi, 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