The ports tree is an huge piece of work that - permits 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 - work better and faster.
+ permits OpenBSD users to use third-party programs without wasting time + patching, configuring and installing each one individually. 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 + cannot help our project because they do not have enough knowledge; + this is false because they can help porters work better and faster.Simply by testing submitted updates or new ports which are posted on +
Testing submitted updates or new ports which are posted on the ports mailing list. By doing this 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 the tester must have in mind that ports development is - done with OpenBSD-current as target.This means - that there is no guarantee that new ports will work correctly on the other - branches. This also means that the tester should upgrade his system to - -current as well as the ports tree (instructions on how to do this can be - found at the anoncvs page and in the - proper faq section. - Having this done, the system is now prepared to do port testing. It is also - advisable the subscription of ports and ports-changes - mailing-lists, this way the tester will be notified - about new/updated ports (to be tested) and about changes in the ports - tree.
+The ports tree is developed against + OpenBSD-current; there is no guarantee that + new ports will work correctly on the other branches. This also means + you should upgrade your system and ports tree to -current + (instructions on how to do this can be found at the + anoncvs page and in the + FAQ). + It is also recommended that you subscribe to the ports and ports-changes + mailing-lists. This way you will be notified + about new or updated ports and about changes in the ports tree.
In the mailing-lists two types of submission can be found; new ports - and updates. New ports are generally posted as tarball attachment - (or an url is given) which contains the port tree. A good idea is to extract - it into the /usr/ports/mystuff/ directory and test the port from here. - Updates are generally a diff against current ports tree, so it is suggested - to copy the port in mystuff/ and apply the diff to prevent tree +
There are two types of submissions on the mailing-lists; new ports + and updates. New ports are generally posted as tarball attachments + or urls. A good idea is to extract them into the + /usr/ports/mystuff/ directory and test from there. + Updates are generally a diff against the -current ports tree, so it is best + to copy the port to mystuff/ and apply the diff to prevent tree breakage.
Step-by-step building is needed to verify that every target, see @@ -79,35 +77,77 @@ ports(7), is achieved correctly :
Checking of pkg/ files like DESCR, MESSAGE, INSTALL, @@ -154,10 +194,9 @@ as well as providing diffs to correct bugs, add flavors, or other enhancements.
$OpenBSD: porttest.html,v 1.7 2002/09/11 09:31:13 couderc Exp $
+
+
$OpenBSD: porttest.html,v 1.8 2002/09/11 12:16:10 avsm Exp $
OpenBSD Copyright © 2002 OpenBSD