[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

checklist.html diff



Here's some minor changes to checklist.html...






--- checklist.html.orig Mon Nov 12 13:01:28 2001
+++ checklist.html   Mon Dec  3 03:34:31 2001
@@ -63,7 +63,7 @@ your ports, including bsd.port.mk.
 <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>
@@ -102,10 +102,14 @@ Set MASTER_SITES to ${MASTER_SITE_GNU}, 
 To simplify this process, the construct %SUBDIR% is replaced by the
variable
 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:
-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. 
+Ports normally correspond to given versions of software. Once they are 
+retrieved, files are checksummed and compared to the recorded 
+checksum(s) in $(PORTSDIR)/distinfo (this used to be
$(PORTSDIR)/files/md5). 
+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>
 If a given port needs more than about 5 DISTFILES + PATCHFILES to work,
use DIST_SUBDIR to avoid cluttering
 /usr/ports/distfiles too much.
@@ -124,7 +128,7 @@ mirror-distfiles will fetch those supple
 </ul>

 <br><li>
-Create a checksum in <i>files/md5</i> by typing <b>make makesum</b>.
+Create a checksum in <i>$(PORTSDIR)/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
@@ -172,11 +176,10 @@ recommend you place the license in <code
 <br><br><li>
 Add configuration options to Makefile and/or create the configuration
script.
 <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. 
+If you need to  add a port configuration script named `configure' you
should
+invoke the script manually through a {pre,do,post}-* target. 
 <li>
-If GNU_CONFIGURE is used you may want to run ./configure --help
+If CONFIGURE_STYLE= gnu 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 +219,7 @@ porters. Ignore this if you haven't set 
 <li>
 Only patch one source file per patchfile, please,
 <li>
-Use <b>diff -p -u</b> to generate patches,
+Use <b>diff -p -u <file.orig> <file> > patch-<file></b> to generate
patches,
 <li>
 All patches MUST be relative to ${WRKDIST},
 <li>
@@ -234,7 +237,7 @@ the patch itself, and an OpenBSD CVS tag
 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
@@ -253,6 +256,8 @@ in <i>/usr/local/share/&lt;name&gt;</i> 
 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
+After a package has been installed the contents of
$(PORTSDIR)/pkg/MESSAGE 
+will be displayed if it exists. 

 <p>
 The OpenBSD file locations are: