Bug#773742: ITP: iortcw -- Return to Castle Wolfenstein

[Simon McVittie <smcv@debian.org>]

On 30/12/14 06:33, Alexandre Detiste wrote:
> For RTCW package:
> - the *.sp.*.so in rtcw-common won't be used by the dedicated, MP-only, server;
>   so they could go in rtcw .

Good point.

> - then I deleted all .pk3 & .cfg symlinks and created new ones to
> /usr/local/games/wolfenstein/

I hadn't realised it would search that directory; I should change the
compile options so it goes for /usr/lib/rtcw by default instead. My
intention had been that it would require the iortcw bits pulled in by
the version of game-data-packager that is also in git.

>  I miss sp_pak4.pk3, mp_bin0.pk3 , mp_rend2_shaders.mp3 , sp_rend2_shaders0.pk3 ;
>  so I get the zenity prompt. I think the "rend2" stuff was iortcw specific ..?

game-data-packager 38 (in git, not yet released) knows how to fetch
these from iortcw: if you run
"game-data-packager rtcw /usr/local/games/wolfenstein" it should do the
right thing.

The iortcw people are releasing de facto official patches which touch
the content (new pk3s), so I don't really intend to support any version
other than "the latest iortcw".

> - lintian complains about manpages; I guess one can use those from
>   the Debian quake3 package (I can help)

If you wouldn't mind adapting the ones from either quake3 or openarena,
that would be great. I don't immediately know which command-line options
are most useful for this game.

I also need to add startup scripts for the dedicated server (like in
quake3/openarena). The dedicated server executable is only a megabyte,
so I might move it into rtcw-common for manual use, and repurpose
rtcw-server for "this package only contains init scripts".

I should also add a Debian menu file at some point, which probably
requires transcoding the .png icon to .xpm during build because the
Debian menu is stuck in the 1990s.

I'm doing all this in parallel with essentially the same things for
openjk (Jedi Outcast and Jedi Academy), which at the moment is compiling
but failing to start up because I got the symlink farm wrong.

    S