Bug#775406: wolf4sdl should be a wrapper script that runs the right engine

[Simon McVittie]

Package: wolf4sdl
Version: 1.7+svn262+dfsg1-2
Severity: wishlist

It seems non-ideal that the user of wolf4sdl is expected to know
which engine they should run. If wolf4sdl was a script rather than an
alternative, it could look at available data and decide which one to run:

vgagraph.wl6 is 275774 bytes: run wolf4sdl-wl6 (1.4 GT/id/Activision)
vgagraph.wl6 is 276096 bytes: run wolf4sdl-wl6 (1.4 GT/id/Activision)
vgagraph.wl6 is 334506 bytes: run wolf4sdl-wl6a (1.4 Apogee)
vgagraph.wl6 is 302374 bytes: unsupported (1.0-1.2)

vgagraph.wl1 is 326568 bytes: run wolf4sdl-wl1 (shareware 1.4)
vgagraph.wl1 is 295394 bytes: unsupported (shareware 1.0)
vgagraph.wl1 is 296826 bytes: unsupported (shareware 1.1)

See data/wolf3d.yaml in game-data-packager git for more sizes, checksums, etc.

(Of course, it would be even better if the upstream code could
detect this at runtime rather than needing to be recompiled with
different #defines, but I realise that probably isn't going to happen.)

Regards,
    S