Annotation of www/porttest.html, Revision 1.6
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:
1.6 ! couderc 7: <title>OpenBSD Port Testing Guide</title>
1.1 couderc 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:
1.6 ! couderc 14: <h2><font color="#e00000">Port Testing Guide</font></h2>
1.1 couderc 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.5 avsm 38: permits OpenBSD users to use third-party programs without losing time in
1.3 couderc 39: patching, configuring, etc. This work is done by a few volunteers who
40: spend hours making your favorite applications work fine on your
1.1 couderc 41: system. Many people think that they can't help our project because they
1.3 couderc 42: don't have enough knowledge; this is false because they can help porters
1.5 avsm 43: work better and faster.</p>
1.1 couderc 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
1.6 ! couderc 48: <a href="mail.html">ports mailing list</a>. By doing this
1.3 couderc 49: you reduce the latency of commits and also increase the number of ports to
50: be committed (many ports are not committed because of lack of testing!).</p>
1.1 couderc 51:
52: <h2><a name="First"><font color="#0000e0">First step</font></a></h2>
53:
1.3 couderc 54: <p>Before starting you must know that ports development is done by
55: following <a href="plus.html">OpenBSD-current</a>; you can find
1.1 couderc 56: instructions on following current <a href="anoncvs.html">source</a> and
57: <a href="faq/upgrade-minifaq.html">upgrade faq</a>. When it's done you
58: are ready to follow <a href=
1.6 ! couderc 59: "mail.html">ports mailing list</a> .</p>
1.1 couderc 60:
61: <h2><a name="Testing"><font color="#0000e0">Testing</font></a></h2>
62:
1.3 couderc 63: <p>Now that you are on the mailing-list you can find two types of
64: submissions; new ports and updates. New ports are generally posted as
65: an attachment or url to a tarball which contains the port tree. A good
66: idea is to extract it into the <tt>/usr/ports/mystuff/</tt> directory
67: and then test it. Updates are generally a diff against the current
68: ports tree, so it is suggested that you copy the port into <tt>mystuff/</tt>
69: and apply the diff to prevent breaking your tree.</p>
1.1 couderc 70:
1.3 couderc 71: <p>You will need to perform step-by-step the building of the port to
1.6 ! couderc 72: verify that every target (see
! 73: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ports&sektion=7&">
! 74: ports(7)</a>) is going correctly :</p>
1.1 couderc 75:
76: <ul>
1.3 couderc 77: <li>fetch : You just need to verify that distfile(s) are correctly
1.1 couderc 78: downloaded.</li>
79:
1.3 couderc 80: <li>extract : Generally extract is done without a problem, so you can
1.1 couderc 81: ignore this target in most cases.</li>
82:
1.3 couderc 83: <li>patch : Check if patches apply correctly and track down forgotten
84: <tt>.orig</tt> .</li>
1.1 couderc 85:
1.3 couderc 86: <li>configure : For ports which use a configure script you can verify
1.1 couderc 87: they have correct path for dependencies, use(less) features, etc
88: ...</li>
89:
1.3 couderc 90: <li>build : The build itself should not give errors but could contain
91: minor warnings about <a href=
1.6 ! couderc 92: "http://www.openbsd.org/cgi-bin/man.cgi?query=tmpnam&sektion=3&">
! 93: tmpnam(3)</a> issues to be resolved by using
! 94: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=mkstemp&sektion=3&">
! 95: mkstemp(3)</a>.</li>
1.1 couderc 96:
1.3 couderc 97: <li>fake : This target is faking installation of the package to prepare
98: for packaging. You should verify that files are installed in fake
1.1 couderc 99: directory.</li>
100:
1.3 couderc 101: <li>package : Package creation can break if pkg/PLIST* and/or
1.1 couderc 102: pkg/PFRAG* are wrong.</li>
103:
1.3 couderc 104: <li>install : Check that package installation works fine.</li>
1.1 couderc 105:
1.3 couderc 106: <li>deinstall : Don't forget to test deinstall.</li>
1.1 couderc 107: </ul>
108:
109: <p>You could also check some pkg/ stuff like DESCR, MESSAGE, INSTALL,
110: DEINSTALL</p>
111:
112: <h2><a name="Commenting"><font color="#0000e0">Commenting</font></a></h2>
113:
114: <p>At the end of the test comes the really important thing : comments.
1.3 couderc 115: Even if the port is working fine you must comment on it. If we have ten
116: posts where people say that the port runs fine under different architectures
117: then the commit is done faster. If it does not work then you must give some
118: information using tools such as <a href=
1.1 couderc 119: "http://www.openbsd.org/cgi-bin/cvsweb/ports/infrastructure/build/portslogger">
120: portslogger</a>.</p>
121:
122: <p>Example :<br>
123: </p>
124:
125: <div style="margin-left: 2em">
126: <table border="0" cellpadding="3" width="100%">
127: <tr>
128: <td nowrap bgcolor="#EEEEEE">
129: <pre>
1.6 ! couderc 130: # make install | /usr/ports/infrastructure/build/portslogger .
1.1 couderc 131: </pre>
132: </td>
133: </tr>
134: </table>
135: </div>
136: <br>
137: <br>
138:
139:
1.3 couderc 140: <p>This will redirect the output into a log file located in the current
1.1 couderc 141: directory.</p>
142:
143: <h2><a name="More"><font color="#0000e0">More testing</font></a></h2>
144:
145: <p>For those who are more skilled they can test targets like
146: lib-depends-check, look at patches and pkg stuff. You can also provide
1.3 couderc 147: diffs to correct bugs, add flavors, or other enhancements.</p>
1.1 couderc 148: <hr>
149:
150: <address>
1.6 ! couderc 151: <p>$OpenBSD: porttest.html,v 1.5 2002/09/10 21:27:36 avsm Exp $<br>
1.4 couderc 152: OpenBSD Copyright © 2002 OpenBSD</p>
1.1 couderc 153: </address>
154: </body>
155: </html>