Annotation of www/porttest.html, Revision 1.2
1.1 couderc 1: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2:
3: <html>
4: <head>
5: <meta http-equiv="content-type" content="text/html; charset=UTF-8">
6:
7: <title>OpenBSD Port's Testing Guide</title>
8: </head>
9:
10: <body text="#000000" bgcolor="#FFFFFF" link="#23238E">
11: <a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src=
12: "images/smalltitle.gif" border="0"></a>
13:
14: <h2><font color="#e00000">Port's Testing Guide</font></h2>
15: <hr>
16:
17: <h2><font color="#0000e0">Index</font></h2>
18:
19: <ul>
20: <li><a href="#Introduction">Introduction</a></li>
21:
22: <li><a href="#How">How</a></li>
23:
24: <li><a href="#First">First step</a></li>
25:
26: <li><a href="#Testing">Testing</a></li>
27:
28: <li><a href="#Commenting">Commenting</a></li>
29:
30: <li><a href="#More">More testing</a></li>
31: </ul>
32: <hr>
33:
34: <h2><a name="Introduction"><font color=
35: "#0000e0">Introduction</font></a></h2>
36:
37: <p>The <a href="ports.html">ports tree</a> is an huge piece of work that
1.2 ! couderc 38: permits to OpenBSD users to use extra stuff without losing time in
1.1 couderc 39: patching, configuring, etc. This work is made by a few volunteers who
40: spend hours to make your favorite applications working fine on your
41: system. Many people think that they can't help our project because they
42: don't have enough knowledge, this is false because they can help porters
43: to work better and faster.</p>
44:
45: <h2><a name="How"><font color="#0000e0">How</font></a></h2>
46:
47: <p>Simply by testing submitted updates or new ports which are posted on
48: <a href="mailto:ports@openbsd.org">ports@openbsd.org</a>. By doing this
49: you reduce the latency of commit and also increase the number of ports to
50: be committed (many ports are not committed because of lack of testing
51: !).</p>
52:
53: <h2><a name="First"><font color="#0000e0">First step</font></a></h2>
54:
55: <p>Before starting you must know that port development is done by
56: following <a href="plus.html">OpenBSD-current</a>, you can find
57: instructions on following current <a href="anoncvs.html">source</a> and
58: <a href="faq/upgrade-minifaq.html">upgrade faq</a>. When it's done you
59: are ready to follow <a href=
60: "mailto:ports@openbsd.org">ports@openbsd.org</a> .</p>
61:
62: <h2><a name="Testing"><font color="#0000e0">Testing</font></a></h2>
63:
64: <p>Now that you are on the mailing-list you can find two type of submits
65: : new ports and updates. New ports are generally posted as an attachment
66: or an url to a tarball which contains the port tree. A good idea is to
67: extract it into the <tt>/usr/ports/mystuff</tt> directory and then you
68: can test it. Updates are generally a diff against current ports tree, so
69: it is suggested to copy the port in mytstuff/ and apply the diff to
70: prevent breaking your tree.</p>
71:
72: <p>You will need to perform step by step the building of the port to
73: verify that every <a href=
74: "http://www.openbsd.org/cgi-bin/man.cgi?query=ports&sektion=7&format=html">
75: target</a> is going right :</p>
76:
77: <ul>
78: <li>fetch : you just need to verify that distfile(s) are correctly
79: downloaded.</li>
80:
81: <li>extract : generally extract is done without problem, so you can
82: ignore this target in most cases.</li>
83:
84: <li>patch : check if patches apply correctly and track down forgotten
85: .orig .</li>
86:
87: <li>configure : for ports which use a configure script you can verify
88: they have correct path for dependencies, use(less) features, etc
89: ...</li>
90:
91: <li>build : the build itself should not give errors but could contain
92: minor warnings about tmpnam issue to be resolved by using mkstemp.</li>
93:
94: <li>fake : this target is faking installation of the package to prepare
95: for packaging. you should verify that files are installed in fake
96: directory.</li>
97:
98: <li>package : package creation can break if pkg/PLIST* and/or
99: pkg/PFRAG* are wrong.</li>
100:
101: <li>install : check that package install works fine.</li>
102:
103: <li>deinstall : don't forget to test deinstall.</li>
104: </ul>
105:
106: <p>You could also check some pkg/ stuff like DESCR, MESSAGE, INSTALL,
107: DEINSTALL</p>
108:
109: <h2><a name="Commenting"><font color="#0000e0">Commenting</font></a></h2>
110:
111: <p>At the end of the test comes the really important thing : comments.
112: Even if the port is working fine you must comment it, if we have ten
113: posts where people say that the port runs fine under different arch then
114: commit is done faster. If it does not work then you must give some
115: information, you have tools for that like <a href=
116: "http://www.openbsd.org/cgi-bin/cvsweb/ports/infrastructure/build/portslogger">
117: portslogger</a>.</p>
118:
119: <p>Example :<br>
120: </p>
121:
122: <div style="margin-left: 2em">
123: <table border="0" cellpadding="3" width="100%">
124: <tr>
125: <td nowrap bgcolor="#EEEEEE">
126: <pre>
127: # make install | /usr/ports/infrastructure/build/portslogger
128: </pre>
129: </td>
130: </tr>
131: </table>
132: </div>
133: <br>
134: <br>
135:
136:
137: <p>This will catch the output into a log file located in the current
138: directory.</p>
139:
140: <h2><a name="More"><font color="#0000e0">More testing</font></a></h2>
141:
142: <p>For those who are more skilled they can test targets like
143: lib-depends-check, look at patches and pkg stuff. You can also provide
144: diff to correct bugs or to add flavors, etc ...</p>
145: <hr>
146:
147: <address>
1.2 ! couderc 148: <p>$OpenBSD: porttest.html,v 1.1 2002/09/10 17:24:50 couderc Exp $<br>
1.1 couderc 149: Copyright © 2002, Damien Couderc, Jim Geovedi, Jose Nazario.</p>
150: </address>
151: </body>
152: </html>
153:
![[BACK]](/icons/back.gif){kind=icon}
Return to porttest.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www