===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/Attic/porttest.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -c -r1.13 -r1.14
*** www/Attic/porttest.html	2002/10/10 11:26:50	1.13
--- www/Attic/porttest.html	2002/11/24 17:08:44	1.14
***************
*** 80,102 ****
      <ul>
        <li><i>fetch</i>
          <ul>
!          <li>Needed to verify that distfile(s) are correctly downloaded. Try to test all of the <tt>MASTER_SITES</tt> specified to make sure they are all valid sources.</li>
          </ul>
  
        <li><i>checksum</i>
          <ul>
!          <li>Verify that downloaded distfiles match the checksums recorded in the <tt>distinfo</tt> file.</li>
          </ul>
  
        <li><i>extract</i>
!         <ul><li>Each of the distfiles should install any dependent programs (such as bzip2) beforehand.</li></ul>
  
        <li><i>patch</i>
          <ul>
           <li>Patches should apply cleanly without any warnings.
           <li>There shouldn't be any <tt>.orig</tt> files left behind in the
               <tt>patches/</tt> directory.
!          <li>Another common mistake is to include RCS tags in a patch; this will break when the port is checked into the repository and the RCS tag expanded.
          </ul>
  
        <li><i>configure</i>
--- 80,108 ----
      <ul>
        <li><i>fetch</i>
          <ul>
!          <li>Needed to verify that distfile(s) are correctly downloaded. Try
!          to test all of the <tt>MASTER_SITES</tt> specified to make sure they
!          are all valid sources.</li>
          </ul>
  
        <li><i>checksum</i>
          <ul>
!          <li>Verify that downloaded distfiles match the checksums recorded
!          in the <tt>distinfo</tt> file.</li>
          </ul>
  
        <li><i>extract</i>
!         <ul><li>Each of the distfiles should install any dependent programs
!         (such as bzip2) beforehand.</li></ul>
  
        <li><i>patch</i>
          <ul>
           <li>Patches should apply cleanly without any warnings.
           <li>There shouldn't be any <tt>.orig</tt> files left behind in the
               <tt>patches/</tt> directory.
!          <li>Another common mistake is to include RCS tags in a patch; this
!          will break when the port is checked into the repository and the RCS
!          tag expanded.
          </ul>
  
        <li><i>configure</i>
***************
*** 117,127 ****
           <li>Warnings about <a href=
        "http://www.openbsd.org/cgi-bin/man.cgi?query=tmpnam&amp;sektion=3&amp;">
        tmpnam(3)</a> issues should be resolved by using
!       <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=mkstemp&amp;sektion=3&amp;"> mkstemp(3)</a>.</li>
!          <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.
          </ul>
  
        <li><i>fake</i>
          <ul>
           <li>This target installs the application into a fake working
--- 123,141 ----
           <li>Warnings about <a href=
        "http://www.openbsd.org/cgi-bin/man.cgi?query=tmpnam&amp;sektion=3&amp;">
        tmpnam(3)</a> issues should be resolved by using
!       <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=mkstemp&amp;sektion=3&amp;">
!           mkstemp(3)</a>.</li>
!          <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.
          </ul>
  
+       <li><i>regress</i>
+         <ul>
+           <li>Check for errors (empty tests means okay).
+         </ul>
+ 
+ 
        <li><i>fake</i>
          <ul>
           <li>This target installs the application into a fake working
***************
*** 169,176 ****
      must be given.
      There are tools that can help in this task, like <a href=
      "http://www.openbsd.org/cgi-bin/cvsweb/ports/infrastructure/build/portslogger">
!     portslogger</a> which is like an "intelligent tee" that redirects output into
!     a log file.</p>
  
      <p>Example :<br>
      </p>
--- 183,190 ----
      must be given.
      There are tools that can help in this task, like <a href=
      "http://www.openbsd.org/cgi-bin/cvsweb/ports/infrastructure/build/portslogger">
!     portslogger</a> which is like an "intelligent tee" that redirects output
!     into a log file.</p>
  
      <p>Example :<br>
      </p>
***************
*** 206,212 ****
      <hr>
  <small>
  <p>
! $OpenBSD: porttest.html,v 1.13 2002/10/10 11:26:50 jufi Exp $
  <br>
        Copyright &copy; 2002 OpenBSD</p>
      </small>
--- 220,226 ----
      <hr>
  <small>
  <p>
! $OpenBSD: porttest.html,v 1.14 2002/11/24 17:08:44 couderc Exp $
  <br>
        Copyright &copy; 2002 OpenBSD</p>
      </small>