www/porttest.html - diff

Return to porttest.html CVS log

Up to [local] / www

Diff for /www/Attic/porttest.html between version 1.2 and 1.3

version 1.2, 2002/09/10 18:43:56

version 1.3, 2002/09/10 19:10:24

Line 35

"#0000e0">Introduction</font></a></h2>

<p>The <a href="ports.html">ports tree</a> is an huge piece of work that

permits to OpenBSD users to use extra stuff without losing time in

permits to OpenBSD users to use third-party programs without losing time in

patching, configuring, etc. This work is made by a few volunteers who

patching, configuring, etc. This work is done by a few volunteers who

spend hours to make your favorite applications working fine on your

spend hours making your favorite applications work fine on your

system. Many people think that they can't help our project because they

don't have enough knowledge, this is false because they can help porters

don't have enough knowledge; this is false because they can help porters

to work better and faster.</p>

<p>Simply by testing submitted updates or new ports which are posted on

<a href="mailto:ports@openbsd.org">ports@openbsd.org</a>. By doing this

you reduce the latency of commit and also increase the number of ports to

you reduce the latency of commits and also increase the number of ports to

be committed (many ports are not committed because of lack of testing

be committed (many ports are not committed because of lack of testing!).</p>

!).</p>

<h2><a name="First"><font color="#0000e0">First step</font></a></h2>

<p>Before starting you must know that port development is done by

<p>Before starting you must know that ports development is done by

following <a href="plus.html">OpenBSD-current</a>, you can find

following <a href="plus.html">OpenBSD-current</a>; you can find

instructions on following current <a href="anoncvs.html">source</a> and

<a href="faq/upgrade-minifaq.html">upgrade faq</a>. When it's done you

are ready to follow <a href=

Line 61

Line 60

<h2><a name="Testing"><font color="#0000e0">Testing</font></a></h2>

<p>Now that you are on the mailing-list you can find two type of submits

<p>Now that you are on the mailing-list you can find two types of

: new ports and updates. New ports are generally posted as an attachment

submissions; new ports and updates. New ports are generally posted as

or an url to a tarball which contains the port tree. A good idea is to

an attachment or url to a tarball which contains the port tree. A good

extract it into the <tt>/usr/ports/mystuff</tt> directory and then you

idea is to extract it into the <tt>/usr/ports/mystuff/</tt> directory

can test it. Updates are generally a diff against current ports tree, so

and then test it. Updates are generally a diff against the current

it is suggested to copy the port in mytstuff/ and apply the diff to

ports tree, so it is suggested that you copy the port into <tt>mystuff/</tt>

prevent breaking your tree.</p>

and apply the diff to prevent breaking your tree.</p>

<p>You will need to perform step by step the building of the port to

<p>You will need to perform step-by-step the building of the port to

verify that every <a href=

"http://www.openbsd.org/cgi-bin/man.cgi?query=ports&sektion=7&format=html">

"http://www.openbsd.org/cgi-bin/man.cgi?query=ports&sektion=7&format=html">target</a> is going correctly :</p>

target</a> is going right :</p>

<ul>

<li>fetch : you just need to verify that distfile(s) are correctly

<li>fetch : You just need to verify that distfile(s) are correctly

downloaded.</li>

<li>extract : generally extract is done without problem, so you can

<li>extract : Generally extract is done without a problem, so you can

ignore this target in most cases.</li>

<li>patch : check if patches apply correctly and track down forgotten

<li>patch : Check if patches apply correctly and track down forgotten

.orig .</li>

<li>configure : for ports which use a configure script you can verify

<li>configure : For ports which use a configure script you can verify

they have correct path for dependencies, use(less) features, etc

...</li>

<li>build : the build itself should not give errors but could contain

<li>build : The build itself should not give errors but could contain

minor warnings about tmpnam issue to be resolved by using mkstemp.</li>

minor warnings about <a href=

"http://www.openbsd.org/cgi-bin/man.cgi?query=tmpnam&sektion=0&format=html">tmpnam</a> issues to be resolved by using <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=mkstemp&sektion=0&format=html">mkstemp</a>.</li>

<li>fake : this target is faking installation of the package to prepare

<li>fake : This target is faking installation of the package to prepare

for packaging. you should verify that files are installed in fake

for packaging. You should verify that files are installed in fake

directory.</li>

<li>package : package creation can break if pkg/PLIST* and/or

<li>package : Package creation can break if pkg/PLIST* and/or

pkg/PFRAG* are wrong.</li>

<li>install : check that package install works fine.</li>

<li>install : Check that package installation works fine.</li>

<li>deinstall : don't forget to test deinstall.</li>

<li>deinstall : Don't forget to test deinstall.</li>

</ul>

<p>You could also check some pkg/ stuff like DESCR, MESSAGE, INSTALL,

Line 109

Line 108

<h2><a name="Commenting"><font color="#0000e0">Commenting</font></a></h2>

<p>At the end of the test comes the really important thing : comments.

Even if the port is working fine you must comment it, if we have ten

Even if the port is working fine you must comment on it. If we have ten

posts where people say that the port runs fine under different arch then

posts where people say that the port runs fine under different architectures

commit is done faster. If it does not work then you must give some

then the commit is done faster. If it does not work then you must give some

information, you have tools for that like <a href=

information using tools such as <a href=

"http://www.openbsd.org/cgi-bin/cvsweb/ports/infrastructure/build/portslogger">

portslogger</a>.</p>

Line 134

Line 133

<br>

<p>This will catch the output into a log file located in the current

<p>This will redirect the output into a log file located in the current

directory.</p>

<h2><a name="More"><font color="#0000e0">More testing</font></a></h2>

<p>For those who are more skilled they can test targets like

lib-depends-check, look at patches and pkg stuff. You can also provide

diff to correct bugs or to add flavors, etc ...</p>

diffs to correct bugs, add flavors, or other enhancements.</p>

<hr>

Line 150

Line 149

</address>

</body>

</html>