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 ports mailing list .
- +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.
+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.
+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 + breakage.
-You will need to perform step-by-step the building of the port to - verify that every target (see +
Step-by-step building is needed to verify that every target, see - ports(7)) is going correctly :
+ ports(7), is achieved correctly :You could also check some pkg/ stuff like DESCR, MESSAGE, INSTALL, - DEINSTALL
+Checking of pkg/ files like DESCR, MESSAGE, INSTALL, + DEINSTALL is also to be done
At the end of the test comes the really important thing : comments. - Even if the port is working fine you must comment on it. If we have ten + Even if the port is working fine comments must be done. If we have ten posts where people say that the port runs fine under different architectures - then the commit is done faster. If it does not work then you must give some - information using tools such as portslogger.
@@ -142,13 +147,16 @@For those who are more skilled they can test targets like - lib-depends-check, look at patches and pkg stuff. You can also provide - diffs to correct bugs, add flavors, or other enhancements.
+Check the port Makefile for typos, incorrect links, useless or + missing variables, correct licensing and correct category. + For those who are more skilled other targets can be tested like + lib-depends-check. Patches and pkg directories deep verification + as well as providing diffs to correct bugs, add flavors, or other + enhancements.
$OpenBSD: porttest.html,v 1.6 2002/09/11 08:49:36 couderc Exp $
+
$OpenBSD: porttest.html,v 1.7 2002/09/11 09:31:13 couderc Exp $
OpenBSD Copyright © 2002 OpenBSD