[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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



On 31/12/14 08:49, Alexandre Detiste wrote:
> It complains about my dubbed pk3

Yeah, I still need to teach the new gdp Python code that some files can
have multiple valid alternatives. For the moment you could apply a local
hack to /usr/share/games/game-data-packager/rtcw-data.yaml (or
data/rtcw-data.yaml if you're running a git checkout) to tell it that
your PK3's size and checksums are the good ones?

> & also about autoexec.cfg (12 bytes, I could brute force it :-) )

It probably isn't copyrightable, it's just "set devdll 1" with no
newline. The MP engine hard-codes devdll to 1 anyway (it's even
CVAR_ROM) and the SP engine doesn't have it, so I'll skip that file
altogether.

>> man pages
>> If you wouldn't mind adapting the ones from either quake3 or openarena,
>> that would be great.
> Ok, I now seen it's done in git.

If you happen to know which cvars and commands are particularly useful,
I'd be happy to take patches. The current version is rather minimal.

>> 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 guess it's better to be consistant with the quake packages.

src:quake is a bit different because it doesn't contain an engine:
quake3 shares the ioquake3 engine with openarena, quake2 has several
viable engines (although only one is in Debian), and quake has two
engines in Debian one of which it shares with nexuiz.

For RTCW and OpenJK I went for simpler packaging in which the engine and
wrapper scripts are bundled together: I don't think either of these
engines is going to be used for a different game any time soon, and
upstream effort seems to have pretty much consolidated around iortcw and
JACoders.

If we do find a need to support more than one RTCW engine fork, we can
make the rtcw* family of binary packages into simple wrappers in
src:quake, and make src:iortcw more like src:ioquake3. Let's cross that
bridge if we come to it, though.

    S


Reply to: