1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="de" lang="de">
5 <base href="http://ftp-master.debian.org/" />
6 <meta http-equiv="content-type" content="text/xhtml+xml; charset=utf-8" />
7 <link type="text/css" rel="stylesheet" href="style.css" />
8 <link rel="shortcut icon" href="http://www.debian.org/favicon.ico" />
10 Debian Archive criteria
16 <a href="http://www.debian.org/">
17 <img src="http://www.debian.org/logos/openlogo-nd-50.png"
18 alt="debian logo" /></a>
19 <a href="http://www.debian.org/">
20 <img src="http://www.debian.org/Pics/debian.png"
21 alt="Debian Project" /></a>
25 <img src="http://www.debian.org/Pics/red-upperleft.png"
26 id="red-upperleft" alt="corner image"/>
28 <img src="http://www.debian.org/Pics/red-lowerleft.png"
29 id="red-lowerleft" alt="corner image"/>
30 <img src="http://www.debian.org/Pics/red-upperright.png"
31 id="red-upperright" alt="corner image"/>
32 <img src="http://www.debian.org/Pics/red-lowerright.png"
33 id="red-lowerright" alt="corner image"/>
35 Debian Archive criteria
40 <table class="DEFINITION">
50 <td>amd64, armel, alpha, m68k. Basically everything that uses
51 the Linux kernel.</td>
55 <td>hurd, opensolaris, kfreebsd. Ports that do not use the
56 Linux kernel, but their own.</td>
62 A new architecture has to follow the <em>Rules for new architectures</em>,
63 and answer all <em>Questions for new architectures</em>.
66 A new OS has to follow the <em>Rules for new architectures</em> and
67 answer all <em>Questions for new architectures</em> as well as all
68 <em>Further questions for OSes</em>.
71 <p>To have the answers all at one location, please create a page below
72 <a href="http://wiki.debian.org/ArchiveQualification/">wiki.debian.org/ArchiveQualification/</a>.
75 <h1>Rules for existing architectures</h1>
78 <li>If an architecture fails to be included in 2 successive
79 official releases, it is moved out of the official archive (and
80 away from the ftp-master.debian.org host).</li>
82 <li>If a removed architecture later can prove it will be able to
83 make the next official release, it can be re-included into the
84 official archive. This step additionally needs the acceptance of
85 the Security, the Release and the Debian Admin Team. (It needs
86 security autobuilders, porter machines, etc.)</li>
89 <h1>Rules for new architectures</h1>
91 <li>A newly included architecture has to be completely built using
92 packages available in plain Debian sources. External patches cannot
95 <li>At the time of inclusion a minimal set of binary packages will be
96 imported into the archive, just enough to get build-essential ready to
97 go and an official buildd setup and running. Everything else will be
98 rebuilt from scratch. As soon as enough is rebuilt to get the initial
99 toolchain built using "native" Debian, this will be rebuilt too.</li>
101 <li>The packages imported from external source and used for the initial
102 build run must be signed by one of the lead porters, who must be a DD.</li>
104 <li>There must be at least two machines ready to be maintained
105 by the Debian System Administrators, so at the start of its
106 lifetime there will be at least one buildd and one porter machine.</br />
108 The inclusion into the archive will almost certainly happen before
109 the machines are handed over to DSA, but this should happen as
110 soon as feasible afterwards.
112 (Note that this is the minimum to get into the archive. The release team
113 may have additional requirements to allow the architecture to release, so
114 there would normally need to be more machines, especially more buildds.)
118 <h1>Questions for new architectures</h1>
120 <!-- <li>Is port cursed?</li> -->
121 <li>Are machines available to buy for the general public?</li>
122 <li>Is full source available?</li>
123 <li>Is this architecture related to other architectures already in
124 the archive, or that also should be considered, either now or in
125 the future? Can the related architectures be supported in a single
126 architecture (eg, with a biarch arrangement)?</li>
127 <li>Are there 3 or more developers (or NMs) actively maintaining
128 the port? Who are they?</li>
129 <li>What sort of architecture is this? Desktop/workstation?
130 Mainframe/supercomputer? Embedded? Something else?</li>
131 <li>Does it have any users? If a desktop system, are there Debian
132 admins who run Debian systems on the arch? If an embedded system
133 are there real systems shipping that a Debian port will be useful
134 for? If a mainframe system are there real systems with many users
135 that a Debian port will be useful for? Who are they?</li>
136 <li>Is there kernel and toolchain support? At what level? Are the
137 latest versions supported, or are legacy releases required for
138 compatability with some hardware?</li>
139 <li>Has the ABI stabalised, or are there major ABI changes coming
140 up? Is the ABI stable enough to ensure users will be able just
141 "apt-get dist-upgrade" from one version to the next?</li>
142 <li>How do you install a system? (URL to a HOWTO)</li>
143 <li>Has a buildd been setup? How much of the archive has been
144 built (count by source package, builds of old versions are fine
146 <li>What hardware is potentially available as a fast buildd?</li>
147 <li>Is there an example box developers can login to to see if it
151 <p>It's also worth considering whether the port has any special
152 requirements. If the port is mainly for embedded systems, it may be
153 appropriate to have different installation or release arrangements
154 compared to normal desktop/workstation architectures.</p>
156 <h1>Further questions for OSes</h1>
159 <li>Are there existing comprehensive free distributions of this OS? If
160 so, why is a Debian distribution useful?</li>
161 <li>What demonstrable benefits does this OS have over existing
163 <li>Does this system have a standard Unix API?</li>
164 <li>Does the OS support modern glibc and gcc?</li>
165 <li>What is the license on the kernel and core libraries? Is the license
166 free? Is the license GPL compatible? (Note that if it's not free, distributing
167 the software violates the Social Contract; and if it's not GPL compatible,
168 GPL software such as dpkg can't be linked to it)</li>
169 <li>Does the OS build largely without source changes? If so, what proportion of
170 the archive has built?</li>
173 <p>It's worth thinking about whether it makes sense to integrate the
174 port with Debian's Linux-based distribution -- having separate sources
175 may not only reduce the impact on the release architectures, but also
176 make it easier to do development on the new OS as well.</p>
178 <p>Note that if significant changes are needed to more than just a small
179 number of packages, your porting team will not only need to provide
180 patches for most of those changes and make sure they work, but also
181 ensure they don't cause problems for existing ports.</p>
186 <a href="http://validator.w3.org/check?uri=referer"><img src="http://www.w3.org/Icons/valid-xhtml10"
187 alt="Valid XHTML 1.0 Strict" height="31" width="88" /></a>
188 <a href="http://jigsaw.w3.org/css-validator/">
189 <img style="border:0;width:88px;height:31px" src="http://jigsaw.w3.org/css-validator/images/vcss"
193 </div> </body> </html>