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