Re: Checklist for packaging games

[Andres Mejia <mcitadel@gmail.com>]

Repeating what's on the wiki.
>  * debian/copyright includes all the copyright and license texts for the
> code and data in the source package

Don't know if this is appropriate, but perhaps a link to 
http://wiki.debian.org/Proposals/CopyrightFormat would help.

>  * All the game data (graphics, fonts, sounds, music, maps, texts, etc) in
> the source package are DFSG-free

Shouldn't this be "All files in source package are DFSG-free, if not, they are 
in seperate source packages or excluded from any source package"

>  * Game compiles with the CFLAGS defined in debian/rules

Or rather, "Game compiles without ignoring flags defined in debian/rules or in 
an environment variable"

>  * Game data is packaged in a separated arch indep (all) package if it's
> big enough
>
>  * Game data is in a separate source package if it is large

Depends on what's defined as "large". Is it >50MB? >650MB? etc.

>  * The binary packages do not include any copy of fonts that are already
> packaged in font packages
>
>  * Executables are installed in /usr/games or /usr/bin

I know in some cases, the game launcher resides in /usr/lib/<game> or 
something similar and it's lauched through a script in /usr/games

>  * Private libraries installed in /usr/lib/<game>/
>
>  * Game loads private libraries through rpath or LD_LIBRARY_PATH

Is this really necessary? After all, they are private.

>  * Game links to public libraries in Debian instead of a private copy of
> them in its source code

Should probably be, "Games builds and uses libraries found in Debian instead 
of equivalent ones that may be found along with source package."

>  * Arch independent files are installed in /usr/share/games/<game>/
>
>  * Arch independent data generation is independent of word length and
> endianess
>
>  * Game loads game data from their absolute paths
>
>  * Game should respect the
> [http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html XDG
> basedir spec]
>
>  * Game saves user data in $HOME/.<game>/ or similar
>
>  * Game loads user data from $HOME/.<game>/ or similar
>
>  * Game inits user data in $HOME/.<game>/ or similar if it is needed
>
>  * Game loads game data independent of the arch endianness and word length
>
>  * Game loads and saves user data independent of the arch endianness and
> word length
>
>  * Patches include copyright and licensing texts
>
>  * A .desktop file is present to start the game

-- 
Regards,
Andres