Bug#693206: vavoom: Let's install the glvis utility

[Fabian Greffrath]

Am 24.12.2012 04:36, schrieb gustavo panizzo <gfa>:
> http://www.vavoom-engine.com/glvis.php says you don't need to use glbsp
> first.

It does not say so explicitely. It merely says that it first searches 
for a GWA file (the one that glbsp creates) and if that does not exist 
it will *assume* that the WAD file already contains the GL nodes.

> i'm using your patch to build vavoom, where you able to use glvis?

Yes, I was able to use it on i386-linux when I introduced the change 
to include it in the package. However, now that I tried it again 
today, I also received a segfault similar to the one that you posted. 
It works flawlessly when rebuilt without "-D_FORTIFY_SOURCE=2", so 
maybe we should replace the offending strcpy() calls with more secure 
alternatives (e.g. strncpy()).

  - Fabian

PS: I disagree with some of the changes that you recently introduced 
into the packaging GIT:

1) There is already a README file for glvis in utils/glvis/glvis.txt, 
so why introduce a new one?

2) The addition of "." and "/" to the "-iwaddir" parameter was in no 
way limited to Boom compatibility. It is, however, strictly needed to 
run the "freedoom" wrapper in Debian, which relies on this feature in 
the "boom" wrapper. But why should it not be possible to run e.g. the 
"doom" wrapper with an Iwad given as a relative or absolute path name?

3) You introduced new wrappers e.g. for doom2. Was this in any way 
arranged with other Doom source ports in Debian?