spear of destiny

[Simon McVittie]

On 08/01/15 08:57, Fabian Greffrath wrote:
> My proposal is the following:
> $nameofgame-($typeofdata-)?-data

I think that makes sense for anything newly supported. For games with
optional music (mainly Quake 1 & 2) I think $GAME-music is also fine -
lots of games in main use that naming.

If I added a new game "Foo" today and it had all the possible flavours
of package (demo/shareware version, full version, an expansion named
"Bar", and some music) then I'd call it foo-demo-data, foo-data,
foo-bar-data, foo-music and foo-bar-music.

If old games' data get renamed, that needs coordination with the
relevant game wrapper/engine maintainers; I suspect it might not be
worth it. In particular, I think we should not rename existing g-d-p
packages unless either the game keeps backwards compat with the old
name, or g-d-p knows how to construct the new .deb from the installed
data (as all YAML ones do) so the user doesn't have to look for their
CDs again.

Here is the complete list of packages that game-data-packager can
produce, categorized by naming pattern.

*-data or *-music, which I think are fine:

hexen2-data
jedi-academy-data
jedi-outcast-data
quake-music
quake-armagon-music
quake-dissolution-music
quake2-demo-data
quake2-full-data
quake2-music
quake3-data
quake3-team-arena-data
rott-data
rtcw-data (I would normally have avoided the acronym but
return-to-castle-wolfenstein-data is pretty unwieldy)
tyrian-data
wolf3d-data

*-wad (doom-common): to be honest I think these are fine to keep as a
historical oddity. It's not as if anyone is writing new proprietary
games on the Doom engine.

doom-wad
doom2-wad
heretic-wad
hexen-wad
plutonia-wad
tnt-wad
    I would personally have made final-doom-data combining TNT and
    Plutonia since AIUI they were only ever sold together, but whatever.
    I don't think g-d-p knew how to put more than one data file in a
    .deb at the time those were added.

others:

lgeneral-data-nonfree
    This one is weird because the proprietary game is actually called
    "Panzer General", but the data gets translated and reformatted
    for the lgeneral engine, which is not actually directly compatible
    with Panzer General; so panzer-general-data would be inappropriate.
    lgeneral-data already exists, in main, so it's lgeneral-data-nonfree
    instead.

    I think this name is fine as an exception; it could have been
    called lgeneral-panzer-general-data, perhaps, but I don't see
    a need to change it now.

quake2-rogue
quake2-xatrix
    I'd have called these quake2-ground-zero-data and
    quake2-reckoning-data if I'd packaged them, because I prefer the
    package name to resemble the "marketing name" (Ground Zero and
    The Reckoning respectively). But it doesn't seem worth changing
    for the sake of changing. Also, these two contain executable code
    (the game DLLs, compiled by g-d-p from non-DFSG source code taken
    from the mod SDK) which is slightly alarming, and means they are
    not entirely "data"; one day I should read through the mod SDK
    license again and see whether we can get that part into non-free.

quake-registered
quake-shareware
quake-armagon
quake-dissolution
    If I did these today I'd call them quake-data,
    quake-(demo|shareware)-data, quake-armagon-data and
    quake-dissolution-data respectively, but it isn't really a big deal.

> Not sure about supplemental data files that need other data files to
> run, e.g. Quake mission packs or the Extreme ROTT levels pack, though.

I think $GAME-$EXPANSION-data is a good rule of thumb, where $GAME and
$EXPANSION are some reasonable abbreviation for the "marketing name" of
the game and the expansion - so rott-extreme-data?

    S