greek/ports/sparc/porting.wml


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67

#use wml::debian::template title="Debian SPARC -- Porting Documentation" NOHEADER="yes"
#include "$(ENGLISHDIR)/ports/sparc/menu.inc"
#use wml::debian::translation-check translation="f9d5abd797e762089776545824869e3e44bd2c42" maintainer="galaxico"

<h1>Debian SPARC Porting Documentation</h1>

<h2>Porting Debian Packages to SPARC</h2>
  <p>
If you want to be an official porter, you must be a registered Debian
developer.  That is, your public key must appear in the official
keyring.
  <p>
The Debian SPARC porting effort is now organized around the excellent
<code>wanna-build</code> system, first used for the <a
href="../m68k/">m68k</a> port.  With <code>wanna-build</code> in
place, porting boils down to locating the packages where automatic
compilation failed, and then going though and determining what went
wrong.
  <p>
Failed build logs can be found at
<a href="https://buildd.debian.org/status/architecture.php?a=sparc64">the SPARC 64 buildd web pages</a>.
Also, you can email <code>wanna-build</code> and ask it for the failed
build logs (see the file <code>README.mail</code> from the
<code>wanna-build</code> distribution).
  <p>
Serious porters should learn how to interact with
<code>wanna-build</code> via email.  You'll need to ask <a
href="mailto:bcollins@debian.org">Ben Collins
&lt;bcollins@debian.org&gt;</a> to add your public key to the known
list of keys.
  <p>
All Debian developers can use Debian's
<a href="https://db.debian.org/machines.cgi">porterbox machines</a> to
test their packages on the SPARC architecture.


<h2>I'm not an official developer; can I still help?</h2>
  <p>
Certainly.  In fact, most of the real work in a Debian port requires
not official status, just knowledge.  There are a number of things you
can do:
<ul>
      <li>
Track down bugs, and report them to the <a href="$(HOME)/Bugs/">Debian
Bug Tracking System</a>.
      <li>
Figure out patches for known bugs.  Be sure to submit the patch to the
Bug Tracking System!
      <li>
Help with documentation.  Most documentation areas are managed under
CVS, and most documentation authors can give out CVS access to
non-porters who are interested in helping.
    </ul>
  <p>
So, go ahead and email <a
href="mailto:debian-sparc@lists.debian.org">&lt;debian-sparc@lists.debian.org&gt;</a>
with a description of how you'd like to help; we're sure someone there
can get you started.


# <!-- Keep this comment at the end of the file
# Local variables:
# mode: sgml
# sgml-indent-data:nil
# sgml-doctype:"../../releases/.doctype"
# End:
# -->