===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/Attic/checklist.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -c -r1.16 -r1.17
*** www/Attic/checklist.html	1999/06/01 22:26:38	1.16
--- www/Attic/checklist.html	1999/08/15 02:23:45	1.17
***************
*** 56,68 ****
         any install docs.  You may need to modify the WRKSRC variable
         in the makefile as well as generate initial patches to configure
         for OpenBSD.
!     <p>Note: Patches go in the directory `patches' and are names patch-xx
         where xx should be aa, ab, ..., az, ba, bb ... zz.
         <ul>
  	<li>only patch one source file per patchfile, please
  	<li>use diff -u to generate patches
  	<li>all patches MUST be relative to ${WRKSRC}
! 	<li>add a small explaination of the patch role in the patchfile before
              the patch itself, and an OpenBSD CVS tag
              <code>&#36;OpenBSD&#36;</code>
         </ul>
--- 56,68 ----
         any install docs.  You may need to modify the WRKSRC variable
         in the makefile as well as generate initial patches to configure
         for OpenBSD.
!     <p>Note: Patches go in the directory `patches' and are named patch-xx
         where xx should be aa, ab, ..., az, ba, bb ... zz.
         <ul>
  	<li>only patch one source file per patchfile, please
  	<li>use diff -u to generate patches
  	<li>all patches MUST be relative to ${WRKSRC}
! 	<li>add a small explanation of the patch role in the patchfile before
              the patch itself, and an OpenBSD CVS tag
              <code>&#36;OpenBSD&#36;</code>
         </ul>
***************
*** 142,149 ****
          Create dummy versions of the package files.  Edit DESCR and COMMENT.
       <p>COMMENT is a <strong>SHORT</strong> one-line description of the port
       (max. 60 characters). Do NOT include the package name (or version number
!      of the software) in the comment. Do NOT start by an uppercase letter
!      unless semantically significant, do NOT end by a dot.
       <p>DESCR is a longer description of the port. One to a few paragraphs
          concisely explaining what the port does is sufficient.
       <p>PLIST is kept empty at this point.
--- 142,149 ----
          Create dummy versions of the package files.  Edit DESCR and COMMENT.
       <p>COMMENT is a <strong>SHORT</strong> one-line description of the port
       (max. 60 characters). Do NOT include the package name (or version number
!      of the software) in the comment. Do NOT start with an uppercase letter
!      unless semantically significant, do NOT end with a period.
       <p>DESCR is a longer description of the port. One to a few paragraphs
          concisely explaining what the port does is sufficient.
       <p>PLIST is kept empty at this point.
***************
*** 175,183 ****
  </pre>
  
     <li>Create pkg/PLIST<br>
!        After the install is complete use the developers command:
      <p><code>make plist</code>
!     <p>which makes a the file PLIST-auto in the pkg directory.  This file
         is a candidate packing list.  Beware: the files are found by
         timestamp.  This means it does NOT:
         <ul>
--- 175,183 ----
  </pre>
  
     <li>Create pkg/PLIST<br>
!        After the install is complete use the developer's command:
      <p><code>make plist</code>
!     <p>which makes the file PLIST-auto in the pkg directory.  This file
         is a candidate packing list.  Beware: the files are found by
         timestamp.  This means it does NOT:
         <ul>
***************
*** 205,211 ****
     <p>
     <li>uninstall and reinstall; repeat until perfect.<br>
         <em>Perfect</em> is when everything installs and uninstalls
!        in its proper location.  `<code>pkg_delete &lt;pkg_name&gt</code>' is
         used to uninstall.  `sudo make reinstall' is used to reinstall.  See the
         `<code>pkg_create</code>' man page for other commands that may be added
         to PLIST to ensure all is cleaned up.  After an uninstall the command
--- 205,211 ----
     <p>
     <li>uninstall and reinstall; repeat until perfect.<br>
         <em>Perfect</em> is when everything installs and uninstalls
!        in its proper location.  `<code>pkg_delete &lt;pkg_name&gt;</code>' is
         used to uninstall.  `sudo make reinstall' is used to reinstall.  See the
         `<code>pkg_create</code>' man page for other commands that may be added
         to PLIST to ensure all is cleaned up.  After an uninstall the command
***************
*** 228,234 ****
  		platforms (the DEC Alpha is good  because it has only static libraries
  		and because sizeof int != sizeof long; Sun SPARC is good because it is
  		very common and because its byte order is the reverse of i386; if you
! 		developed on SPARC, of course, y ou'd want it tested on i386).
  		<P>The ports@openbsd mailing list is a good place to find porting-savy
  		people with different platforms!
  		<li>Incorporate any feedback you get. Test it again on your platform.
--- 228,234 ----
  		platforms (the DEC Alpha is good  because it has only static libraries
  		and because sizeof int != sizeof long; Sun SPARC is good because it is
  		very common and because its byte order is the reverse of i386; if you
! 		developed on SPARC, of course, you'd want it tested on i386).
  		<P>The ports@openbsd mailing list is a good place to find porting-savy
  		people with different platforms!
  		<li>Incorporate any feedback you get. Test it again on your platform.
***************
*** 301,306 ****
    <a href="porting.html"><img height=24 width=24 src=back.gif
     border=0 alt=Porting></a> 
    <a href="mailto:www@openbsd.org">www@openbsd.org</a>
!   <br><small>$OpenBSD: checklist.html,v 1.16 1999/06/01 22:26:38 espie Exp $</small>
   </body>
  </html>
--- 301,306 ----
    <a href="porting.html"><img height=24 width=24 src=back.gif
     border=0 alt=Porting></a> 
    <a href="mailto:www@openbsd.org">www@openbsd.org</a>
!   <br><small>$OpenBSD: checklist.html,v 1.17 1999/08/15 02:23:45 marc Exp $</small>
   </body>
  </html>