The ports tree is an huge piece of work that - permits to OpenBSD users to use extra stuff without losing time in - patching, configuring, etc. This work is made by a few volunteers who - spend hours to make your favorite applications working fine on your + permits to OpenBSD users to use third-party programs without losing time in + patching, configuring, etc. This work is done by a few volunteers who + 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.
Simply by testing submitted updates or new ports which are posted on ports@openbsd.org. By doing this - you reduce the latency of commit and also increase the number of ports to - be committed (many ports are not committed because of lack of testing - !).
+ 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!).Before starting you must know that port development is done by - following OpenBSD-current, you can find +
Before starting you must know that ports development is done by + following OpenBSD-current; you can find instructions on following current source and upgrade faq. When it's done you are ready to follow Testing -
Now that you are on the mailing-list you can find two type of submits - : new ports and updates. New ports are generally posted as an attachment - or an url to a tarball which contains the port tree. A good idea is to - extract it into the /usr/ports/mystuff directory and then you - can test it. Updates are generally a diff against current ports tree, so - it is suggested to copy the port in mytstuff/ and apply the diff to - prevent breaking your tree.
+Now that you are on the mailing-list you can find two types of + submissions; new ports and updates. New ports are generally posted as + an attachment or url to a tarball which contains the port tree. A good + idea is to extract it into the /usr/ports/mystuff/ directory + and then test it. Updates are generally a diff against the current + ports tree, so it is suggested that you copy the port into mystuff/ + and apply the diff to prevent breaking your tree.
-You will need to perform step by step the building of the port to +
You will need to perform step-by-step the building of the port to verify that every - target is going right :
+ "http://www.openbsd.org/cgi-bin/man.cgi?query=ports&sektion=7&format=html">target is going correctly :You could also check some pkg/ stuff like DESCR, MESSAGE, INSTALL, @@ -109,10 +108,10 @@
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 - posts where people say that the port runs fine under different arch then - commit is done faster. If it does not work then you must give some - information, you have tools for that like portslogger.
@@ -134,20 +133,19 @@This will catch the output into a log file located in the current +
This will redirect the output into a log file located in the current directory.
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 ...
+ diffs to correct bugs, add flavors, or other enhancements.$OpenBSD: porttest.html,v 1.2 2002/09/10 18:43:56 couderc Exp $
+
$OpenBSD: porttest.html,v 1.3 2002/09/10 19:10:24 couderc Exp $
Copyright © 2002, Damien Couderc, Jim Geovedi, Jose Nazario.