===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/Attic/checklist.html,v
retrieving revision 1.32
retrieving revision 1.33
diff -c -r1.32 -r1.33
*** www/Attic/checklist.html	2001/04/02 20:44:58	1.32
--- www/Attic/checklist.html	2001/07/05 18:52:09	1.33
***************
*** 17,23 ****
  <h2><font color="#e00000">OpenBSD Porting Checklist</font></h2>
  
  This document describes how to make or upgrade a port.  It is a useful
! reminder of things to do.  This is not totally accurate nor perfect.
  Direct comments and questions to <a href="mailto:ports@openbsd.org"> 
  ports@openbsd.org </a>.
  
--- 17,23 ----
  <h2><font color="#e00000">OpenBSD Porting Checklist</font></h2>
  
  This document describes how to make or upgrade a port.  It is a useful
! reminder of things to do.  This is neither totally accurate nor perfect.
  Direct comments and questions to <a href="mailto:ports@openbsd.org"> 
  ports@openbsd.org </a>.
  
***************
*** 32,38 ****
  <li>
  Reading this list is important since many announcements go over this list.
  <li>
! You will find a lot of porting-savvy people here.  They can often give you
  good advice or test ports for you.
  </ul>
  
--- 32,38 ----
  <li>
  Reading this list is important since many announcements go over this list.
  <li>
! You will find a lot of porting-savvy people there.  They can often give you
  good advice or test ports for you.
  </ul>
  
***************
*** 43,49 ****
  
  <br><li>
  Check out a copy of the ports tree from cvs. 
! You can find instructions to do this at
  <a href="http://www.openbsd.org/anoncvs.html">
  http://www.openbsd.org/anoncvs.html</a>.
  
--- 43,49 ----
  
  <br><li>
  Check out a copy of the ports tree from cvs. 
! You can find instructions on how to do this at
  <a href="http://www.openbsd.org/anoncvs.html">
  http://www.openbsd.org/anoncvs.html</a>.
  
***************
*** 85,91 ****
  ${MASTER_SITES}${DISTNAME}${EXTRACT_SUFX}.  All three are used.  Don't
  set DISTNAME to point to the file directly.
  <li>
! You can check to see if you have filled this values in correctly by typing
  <b>make fetch-all</b> 
  </ul>
  <p>
--- 85,91 ----
  ${MASTER_SITES}${DISTNAME}${EXTRACT_SUFX}.  All three are used.  Don't
  set DISTNAME to point to the file directly.
  <li>
! You can check to see if you have filled these values in correctly by typing
  <b>make fetch-all</b> 
  </ul>
  <p>
***************
*** 143,149 ****
  
  <br><li>
  Extract the port with <b>make extract</b>.  Pay attention to where the base 
! of the sources are.  Usually, its <i>work/DISTNAME</i> You may need to modify 
  the Makefile's WRKDIST variable if it is different.
  
  <br><br><li>
--- 143,149 ----
  
  <br><li>
  Extract the port with <b>make extract</b>.  Pay attention to where the base 
! of the sources are.  Usually, it's <i>work/DISTNAME</i>. You may need to modify 
  the Makefile's WRKDIST variable if it is different.
  
  <br><br><li>
***************
*** 152,158 ****
  
  <br><br><li>
  Now is also a good time to figure out what kind of licensing restrictions
! apply to your port.  Many are freely redistribution but then again, quite
  a few are not.  We need four questions answered to distribute ports 
  properly.  These are the PERMIT_* values in the Makefile.
  <ul><li>
--- 152,158 ----
  
  <br><br><li>
  Now is also a good time to figure out what kind of licensing restrictions
! apply to your port.  Many are freely redistributable but then again, quite
  a few are not.  We need four questions answered to distribute ports 
  properly.  These are the PERMIT_* values in the Makefile.
  <ul><li>
***************
*** 192,198 ****
  If you're lucky, the port will go all the way through without errors.  
  <li>
  If it exits with an error, you will need to generate patches for your port.  
! Figure out what needs to be changed and make patch for it.  
  <li>
  Patches must be relative to ${WRKDIST}.  
  <li> The easiest way to reset the port and test your patches is 
--- 192,198 ----
  If you're lucky, the port will go all the way through without errors.  
  <li>
  If it exits with an error, you will need to generate patches for your port.  
! Figure out what needs to be changed and make a patch for it.  
  <li>
  Patches must be relative to ${WRKDIST}.  
  <li> The easiest way to reset the port and test your patches is 
***************
*** 339,345 ****
  
  <li>
  Create pkg/PLIST.  After the install is complete use the developer's command,
! <b>make plist</b> which makes the file PLIST-auto in the <i>pkg</i> directory. 
  This file is a candidate packing list.  
  <p>
  Beware! The files are found by timestamp.  This means it does NOT:
--- 339,345 ----
  
  <li>
  Create pkg/PLIST.  After the install is complete use the developer's command,
! <b>make plist</b> which makes the file PLIST in the <i>pkg</i> directory. 
  This file is a candidate packing list.  
  <p>
  Beware! The files are found by timestamp.  This means it does NOT:
***************
*** 357,380 ****
  anything in the packing list.  But still...
  </ul>
  <p>
! Peruse `PLIST-auto' and verify that everything was installed and
  that it was installed in the proper locations.  Anything not installed
  can be added to a port Makefile `post-install' rule.
- <p>
- Move `PLIST-auto' to `PLIST'
  
  <p>
! Ports that install shared libraries will need two versions of the PLIST file.  
  <ul>
  <li>
! PLIST describes the files installed on those architectures that support 
! shared libraries.
  <li>
! PLIST.noshared describes the files installed on architectures that do not 
! support shared libs.
! <li>
! Typically, PLIST.noshared is a copy of PLIST less references to any 
  shared libraries.
  </ul>
  
  <br><li>
--- 357,377 ----
  anything in the packing list.  But still...
  </ul>
  <p>
! Peruse `PLIST' and verify that everything was installed and
  that it was installed in the proper locations.  Anything not installed
  can be added to a port Makefile `post-install' rule.
  
  <p>
! Ports that install shared libraries will have another file called PFRAG.shared.  
  <ul>
  <li>
! PLIST describes the files being independent of whether the architecture supports shared libraries or not.
  <li>
! PFRAG.shared describes only the files being additionally installed on those architectures that support 
  shared libraries.
+ <li>
+ PFRAG.noshared describes only the files being additionally installed on architectures that do not 
+ support shared libraries.
  </ul>
  
  <br><li>
***************
*** 384,390 ****
  used to uninstall.  `sudo make reinstall' is used to reinstall.  See the
  `pkg_create' man page for other commands that may be added
  to PLIST to ensure all is cleaned up.  After an uninstall the command
! <p><code>find /usr/local -newer work/.install_started -print</code>
  <p>should only list standard directory names.
  
  <br><br><li>
--- 381,387 ----
  used to uninstall.  `sudo make reinstall' is used to reinstall.  See the
  `pkg_create' man page for other commands that may be added
  to PLIST to ensure all is cleaned up.  After an uninstall the command
! <p><code>find /usr/local -newer work/fake-${MACHINE_ARCH}[-${FLAVOR}]/.install_started -print</code>
  <p>should only list standard directory names.
  
  <br><br><li>
***************
*** 496,501 ****
  <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.32 2001/04/02 20:44:58 naddy Exp $</small>
  </body>
  </html>
--- 493,498 ----
  <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.33 2001/07/05 18:52:09 pvalchev Exp $</small>
  </body>
  </html>