===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/Attic/porttest.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- www/Attic/porttest.html	2005/02/09 20:37:25	1.19
+++ www/Attic/porttest.html	2005/12/20 08:33:09	1.20
@@ -38,7 +38,8 @@
     <h2><a name="Introduction"><font color=
     "#0000e0">Introduction</font></a></h2>
 
-    <p>The <a href="ports.html">ports tree</a> is an huge piece of work that
+    <p>The <a href="faq/faq15.html#Ports">ports tree</a> is a huge piece
+    of work that
     permits OpenBSD users to use third-party programs without wasting time 
     patching, configuring and installing each one individually. This work 
     is done by a group of volunteers who spend their time porting and testing
@@ -58,7 +59,8 @@
 
     <p>The ports tree is developed against 
     <a href="plus.html">OpenBSD-current</a>; there is no guarantee that 
-    new ports will work correctly on the other branches. This also means 
+    new ports or updates will work correctly on the other branches.
+    This means 
     you should upgrade your system and ports tree to -current 
     (instructions on how to do this can be found at the 
     <a href="anoncvs.html">anoncvs</a> and 
@@ -71,7 +73,7 @@
 
     <p>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 
+    or URLs. A good idea is to extract them into the 
     <tt>/usr/ports/mystuff/</tt> directory and test from there.
     Updates are generally a diff against the -current ports tree, so it is best 
     to copy the port to <tt>mystuff/</tt> and apply the diff to prevent tree
@@ -132,6 +134,10 @@
          <li>Try to set the <tt>SEPARATE_BUILD</tt> variable to 'concurrent'
          and test if the build still works.
          <li>Make sure dependencies on GNU make are really necessary.
+         <li>Check whether the port is using libtool. If it is, try
+         setting <tt>USE_LIBTOOL=Yes</tt>. This way, the ports
+         infrastructure will use the libtool version in the tree, instead
+         of libtool versions that come bundled with the software's source.
         </ul>
 
       <li><i>regress</i>
@@ -147,8 +153,12 @@
          without affecting the base system.
          <li>The port should <b>never</b> install files outside of the
          fake directory (such as into <tt>/usr/local</tt>).
+         This kind of mistake can be easily caught by using
+         <tt>USE_SYSTRACE=Yes</tt>.
          <li>GNU libtool occasionally has trouble relinking libraries
          during the fake process on some architectures.
+         <li>Check whether all files get installed with correct ownerships
+         and permissions.
         </ul>
 
       <li><i>package</i>
@@ -157,6 +167,14 @@
          pkg/PFRAG* are wrong.</li>
         </ul>
 
+      <li><i>lib-depends-check</i>
+        <ul>
+         <li>This will check whether all libraries on which the port depends
+         can be reached through either <tt>LIB_DEPENDS</tt> or <tt>WANTLIB</tt>.
+         The result should be empty. The above variables should be inspected
+         when you see lines starting "Extra" or "Missing".
+        </ul>
+
       <li><i>install</i>
         <ul>
          <li>Packages should install all of the files from their packaging
@@ -211,13 +229,17 @@
     <p>This will redirect the output into a log file located in the current
     directory.</p>
 
+    <p>Finally, once the port is found to be okay, other ports depending on
+    it should also be tested, to check whether they are still working
+    correctly. The <i>show-required-by</i> make target will help to find
+    other ports which depend on the current one.
+
     <h2><a name="More"><font color="#0000e0">More testing</font></a></h2>
 
-    <p>Check the port Makefile for typos, incorrect links, useless or
-    missing variables, correct licensing and categories.
-    For those who are more skilled other targets can be tested like
-    <i>lib-depends-check</i>, examining patches, as well as providing
-    diffs to correct bugs, add flavors, or other enhancements.</p>
+    <p>Check the port's Makefile for correct dependencies, typos, incorrect
+    links, useless or missing variables, correct licensing and categories.
+    Those who are more skilled can help by examining patches, as well as
+    providing diffs to correct bugs, add flavors, or other enhancements.</p>
     <p>These diffs should be done with the <tt>-uNr --exclude=CVS</tt> options.
     <tt>cvs diff -uN</tt> can also be used to generate patches against
     the CVS repository.</p>
@@ -225,7 +247,7 @@
 <a href="index.html"><img src="back.gif" height="24" width="24" alt="OpenBSD" border="0"></a>
 <a href="mailto:www@openbsd.org">www@openbsd.org</a><br>
 <small>
-$OpenBSD: porttest.html,v 1.19 2005/02/09 20:37:25 nick Exp $
+$OpenBSD: porttest.html,v 1.20 2005/12/20 08:33:09 steven Exp $
 </small>
 </body>
 </html>