===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/Attic/checklist.html,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- www/Attic/checklist.html	2001/11/12 21:01:28	1.39
+++ www/Attic/checklist.html	2001/12/19 21:33:48	1.40
@@ -63,7 +63,7 @@
 <br>
 
 <ul><li>
-Create the directories <code>files, patches, pkg</code>.
+Create the directories <code>patches, pkg</code>.
 <li>
 Create these empty files <code>pkg/DESCR, pkg/PLIST</code>
 </ul>
@@ -103,7 +103,7 @@
 MASTER_SITE_SUBDIR in your Makefile.
 <li>
 Ports normally correspond to given versions of software. Once they are retrieved, files are checksummed and compared to the recorded
-checksum in files/md5. So, to avoid confusion, DISTFILES and PATCHFILES should have clearly visible version numbers:
+checksum(s) in distinfo. So, to avoid confusion, DISTFILES and PATCHFILES should have clearly visible version numbers:
 don't retrieve foo-latest.tar.gz if it is a link to foo-1.0.5.tar.gz. If necessary, gently ask the original program author
 to make such distinctions clear. 
 <li>
@@ -124,7 +124,7 @@
 </ul>
 
 <br><li>
-Create a checksum in <i>files/md5</i> by typing <b>make makesum</b>.
+Create a checksum in <i>distinfo</i> by typing <b>make makesum</b>.
 Then verify the checksum is correct by typing <b>make checksum</b>
 <ul><li>
 In some rare cases, files checksums can't be verified reliably. By all means, porters should try to find sites that are reliable. Communicating
@@ -174,9 +174,9 @@
 <ul><li>
 You can add a port configuration script named `configure' to a directory 
 named <code>scripts/</code>. This will be run before any configuration 
-specified by GNU_CONFIGURE or HAS_CONFIGURE is run. 
+specified by CONFIGURE_STYLE is run. 
 <li>
-If GNU_CONFIGURE is used you may want to run ./configure --help
+If GNU configure is used you may want to run ./configure --help
 to see what options are available.  
 <li>
 Anything that you may want to override can be changed by adding the 
@@ -216,7 +216,7 @@
 <li>
 Only patch one source file per patchfile, please,
 <li>
-Use <b>diff -p -u</b> to generate patches,
+Use <b>make update-patches</b> to generate patches,
 <li>
 All patches MUST be relative to ${WRKDIST},
 <li>
@@ -234,7 +234,7 @@
 Try setting <code>SEPARATE_BUILD</code><br>
 <ul><li>
 If the port can build with object files outside its source tree,
-this is cleaner (many programs using <code>GNU_CONFIGURE</code> can),
+this is cleaner (many programs using <code>CONFIGURE_STYLE=gnu</code> can),
 and may help people who mount their ports tree on several arches.
 <li>
 This can also spare you some effort, as you will possibly be able to
@@ -252,7 +252,9 @@
 <i>/etc</i> or <i>/etc/&lt;name&gt;</i> only if the files do not exist.
 If the files exist, display a message that says such-and-such files need
 to be modified.  This also guarantees that the files will be included in
-the package since everything under <i>/usr/local</i> is included in the PLIST
+the package since everything under <i>/usr/local</i> is included in the PLIST.
+After a package has been installed the contents of <code>pkg/MESSAGE</code>
+will be displayed if it exists.
 
 <p>
 The OpenBSD file locations are:
@@ -499,6 +501,6 @@
 <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.39 2001/11/12 21:01:28 jufi Exp $</small>
+<br><small>$OpenBSD: checklist.html,v 1.40 2001/12/19 21:33:48 naddy Exp $</small>
 </body>
 </html>