Bug#776280: g-d-p: please add support for No Rest For The Living

[Simon McVittie]

On 08/02/15 14:03, Alexandre Detiste wrote:
>> As an aside, please don't call it "norest", noone calls it like that.
>> It's simply "nerve", just as the WAD is called. This is even how it is
>> refered to in the official sources:
> 
> This bring us back to the discussion of "marketing names" versus codenames.

I continue to believe that a package name that is (an obvious
abbreviation for) the game's "marketing name" is a better choice than
what the game engine calls it internally. quake3-team-arena-data, not
quake3-missionpack; doom3-data, not neo-data :-)

>> So, this is the current situation in my /us/share/games/doom directory:
>>
>> $ find /usr/share/games/doom/ -name doom2.wad
>> /usr/share/games/doom/xbox/doom2.wad
>> /usr/share/games/doom/psn/doom2.wad
>> /usr/share/games/doom/bfg/doom2.wad
>> /usr/share/games/doom/doom2.wad
>> /usr/share/games/doom/xbox360/doom2.wad
>  
>> Could you tell me _which_ of these files is the one that ends up in the
>> doom2-wad package that g-d-p creates?
> I can't tell, G-D-P would choose a file at random; but dpkg -i will only overwrite 
> /usr/share/games/doom/doom2.wad .

I think g-d-p is actually deterministic here: it will use the first wad
in the list of alternatives, currently "doom2.wad_1.9" (90s Doom 2
v1.9). If you don't have that one, it will continue down the list: the
one from Doom 3 BFG Edition is (fairly arbitrarily) next on the list.

If you know that some of the versions of doom2.wad are better than
others by some metric, we can re-order the list; or if some of the
console editions don't actually work on source ports, we can remove them.

The resulting .deb will overwrite .../doom/doom2.wad and leave the
others intact, as Alexandre said.

    S