DISCLAIMER: this is still a stub and not the official policy of the Debian Games Team
Instead please follow the team's guidelines
Debian/Ubuntu Games Team Policy
creating new packages
- All binaries must have menu and desktop files.
- Bonus-ponies for translations and useful comments.
- Libraries do not need menu/desktop files
Clarify to "All executables intended to be run by the end-user must..." or "All executables in $PATH must..." or something? /usr/lib/ioquake3/ioquake3 is the real Quake 3 engine binary but is only intended to be invoked via wrapper scripts. --SimonMcVittie
- There should be no “pwd” occurrences in debian/rules. Depending on the context, that can cause FTBFSes. This one might be forwarded to lintian authors. $(CURDIR) is preferable.
$PWD is worse than pwd, as I understand it? --SimonMcVittie
- debian/control should have a Homepage field linking to the upstream homepage (if any) and Vcs-* fields linking to pkg-games VCS.
- The package must be in a (D)VCS as part of the games team. It can be Git or SVN, and must contain at least a debian/ directory.
making changes to existing packages
Changing/updating all packages is encouraged. - not only your own
- Please do not override maintainers decisions (build-system, patch-system, VCS, etc).
- Updating to the latest debhelper version is considered fine, though (if packaging does not contain a comment in debian/rules that one should not do such an update).
- Not yet ready packages should have UNRELEASED in debian/changelog.
- Packages targeted at experimental should state so as the first entry in the changelog.
- Packages with unstable/experimental in debian/changelog are ready-to-upload.
- Uploaded packages should be tagged in the VCS after the upload.
- In the case of a sponsored upload the sponsoring DD should tag (if he is part of pkg-games).
Set the Maintainer field to "Debian Games Team <email@example.com>" and add yourself to the Uploaders field.
pkg-games lintian checks
- do we want own lintian checks?