From: Joerg Jaspert Date: Sun, 29 Mar 2009 21:13:44 +0000 (+0200) Subject: archive criteria X-Git-Url: https://err.no/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e724d6c64d686c5efda9def318a3b21f50426bf2;p=dak archive criteria merge the "old" criteria together with the "new" rules into one document. Signed-off-by: Joerg Jaspert --- diff --git a/web/archive-criteria.html b/web/archive-criteria.html index 47c22062..39b16d29 100644 --- a/web/archive-criteria.html +++ b/web/archive-criteria.html @@ -1,77 +1,193 @@ - -

Really crappy page documenting archive criteria

- -

Architectures

- -

Release candidates: alpha, amd64, hppa, i386, ia64, mips, mipsel, powerpc -
Release hopefuls: arm, s390, sparc - -

Requalification expected: m68k -
Future linux ports: armeb -
New OS hopefuls: kfreebsd-i386, win32-i386 - -

Requirements for architectures

- -

Examples: amd64, arm, armeb, m68k, s390, sparc - -

- -

It's also worth considering whether the port has any special -requirements. If the port is mainly for embedded systems, it may be -appropriate to have different installation or release arrangements -compared to normal desktop/workstation architectures. - -

Further requirements for OSes

- -

Examples: hurd, opensolaris, kfreebsd - -

- -

It's worth thinking about whether it makes sense to integrate the -port with Debian's Linux-based distribution -- having separate sources -may not only reduce the impact on the release architectures, but also -make it easier to do development on the new OS as well. - -

Note that if significant changes are needed to more than just a small -number of packages, your porting team will not only need to provide -patches for most of those changes and make sure they work, but also -ensure they don't cause problems for existing ports. - - - + + + + + + + + + Debian Archive criteria + + + + +

+
+ + corner image + + corner image + corner image + corner image + + Debian Archive criteria + +
+ +

Definitions

+ + + + + + + + + + + + + + + + + +
 Example
Architectureamd64, armel, alpha, m68k. Basically everything that uses + the Linux kernel.
OShurd, opensolaris, kfreebsd. Ports that do not use the + Linux kernel, but their own.
+ +

+ A new architecture has to follow the Rules for new architectures, + and answer all Questions for new architectures. +

+

+ A new OS has to follow the Rules for new architectures and + answer all Questions for new architectures as well as all + Further questions for OSes. +

+ +

To have the answers all at one location, please create a page below + wiki.debian.org/ArchiveQualification/. +

+ +

Rules for existing architectures

+ + + +

Rules for new architectures

+ + +

Questions for new architectures

+ + +

It's also worth considering whether the port has any special + requirements. If the port is mainly for embedded systems, it may be + appropriate to have different installation or release arrangements + compared to normal desktop/workstation architectures.

+ +

Further questions for OSes

+ + + +

It's worth thinking about whether it makes sense to integrate the + port with Debian's Linux-based distribution -- having separate sources + may not only reduce the impact on the release architectures, but also + make it easier to do development on the new OS as well.

+ +

Note that if significant changes are needed to more than just a small + number of packages, your porting team will not only need to provide + patches for most of those changes and make sure they work, but also + ensure they don't cause problems for existing ports.

+ + +