Re: d-i policy
On Wed, Oct 01, 2003 at 02:50:21AM -0700, Matt Kraai wrote:
> Here is my first draft of a d-i policy guide. I've folded in the
> requirements from cheatsheet.txt (which is obsoleted and removed),
> as well as some recent list discussions.
> Any objections?
I changed the menu-entry title and subarchitecture field parts to
use "should" instead of "must" since they are not widely
I'll commit the following patch tomorrow unless someone objects.
RCS file: doc/cheatsheet.txt
diff -N doc/cheatsheet.txt
--- doc/cheatsheet.txt 21 Mar 2003 18:47:16 -0000 1.3
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,10 +0,0 @@
-Random things to remember (please add to this list)
-- When changing in debconf templates, remember to run debconf2po-update so
- the files in the po directory will be updated.
-- Releases are tagged as in cvs-buildpackage, that is
- debian_version_0_0_1 for version 0.0.1.
-- Make sure you don't include md5sums inside the package. Remove
- call to dh_md5sums from debian/rules if present.
RCS file: doc/policy.txt
diff -N doc/policy.txt
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ doc/policy.txt 2 Oct 2003 08:48:38 -0000
@@ -0,0 +1,46 @@
+Debian GNU/Linux Installer Policy
+This document describes the policy requirements for the Debian
+GNU/Linux installer. You must ask firstname.lastname@example.org before
+Installer packages that have a menu entry must have an
+installer-menu-item header whose value must be a number indicating the
+priority of the package. The value must chosen by asking
+email@example.com and must be recorded in
+Installer packages that have a menu entry should have a
+debian-installer/<package>/title template whose description is the
+text of the menu entry.
+Installer packages that should only be installed and configured on
+particular subarchitectures should have a Subarchitecture field that
+contains a white space separated list of the subarchitectures on which
+they work. Each subarchitecture must be one of the following:
+ * powerpc_oldworld
+ * powerpc_newworld
+ * prep
+ * chrp_pegasos
+ * chrp
+ * amiga
+ * unknown
+ * generic
+Installer packages must not include md5sums.
+Installer Packages Hosted at cvs.debian.org
+Installer packages hosted on cvs.debian.org must keep the debian/po
+directory in sync with their templates.
+Installer packages hosted on cvs.debian.org must have their releases
+tagged. The tags must be of the form
+ debian_release_<version number with . replaced by _>
- d-i policy
- From: Matt Kraai <firstname.lastname@example.org>