===================================================================
RCS file: /cvsrepo/anoncvs/cvs/ports/README,v
retrieving revision 1.6
retrieving revision 1.9
diff -u -r1.6 -r1.9
--- ports/README	1999/09/26 10:52:55	1.6
+++ ports/README	2001/02/21 23:23:13	1.9
@@ -6,21 +6,23 @@
 			http://www.openbsd.org
 
 
-When things go wrong
-====================
-There are several contacts for the ports tree.
+Contacts
+========
 * individual ports list a 
 MAINTAINER=  
-line in their Makefile.  Try to contact that person first.
+line in their Makefile.  
 * specific issues related to the ports framework (e.g., bugs in
 bsd.port.mk)  should go to ports-admin@openbsd.org
 * ports without explicit maintainers, and other general issues should
 go to ports@openbsd.org
 
-As a general rule, try to contact the MAINTAINER first.  If nothing happens
-after a reasonable delay, start plaguing him, or go to the next step.
+Considering the size of the ports tree, and even though we strive to
+eradicate all bugs, things may go wrong on individual ports.  
+In such a case, as a general rule, try to contact the MAINTAINER first.  
+If nothing happens after a reasonable delay, start plaguing him, 
+or go to the next step.
 
-Developpers with a major investment in the ports tree include
+Developers with a major investment in the ports tree include
 brad@cvs.openbsd.org, turan@cvs.openbsd.org, espie@cvs.openbsd.org
 
 Those people can be contacted to put some pressure on a lazy maintainer.
@@ -31,7 +33,7 @@
 The ports tree usually live under /usr/ports. It's a hierarchical
 list of recipes to build various pieces of software.
 We'll call that PORTSDIR in the following discussion.
-Stuff that doesn't constitue a port proper, but rather paraphernalia,
+Stuff that doesn't constitute a port proper, but rather paraphernalia,
 is stored under /usr/ports/infrastructure, INFRA in the following
 discussion.
 
@@ -110,9 +112,10 @@
 * `make distclean CLEANDEPENDS=Yes', guess what this does.
 
 Please note that, in normal use, the OpenBSD ports tree will grow quite
-a lot.  Careful use of make clean and make distclean will help you.
-`find /usr/ports -type d -name work\* -print' can be useful to find out
-ports you forgot to clean out.
+a lot.  Careful use of make clean and make distclean will help you. You
+can also redirect ports activity elsewhere by making use of WRKOBJDIR
+and DISTDIR.  `find /usr/ports -type d -name work\* -print' 
+can be useful to find out ports you forgot to clean out.
 
 There are a few kinks in the building of ports with options yet. Namely,
 all such ports should produce distinct package names if built with
@@ -177,7 +180,7 @@
 
 Continuing our CD-Rom example, you could also fetch files off a CD-Rom into
 your repository for safe-keeping by using the following incantation:
-make fetch MASTER_SITE_OVERRIDE='file:/cdrom/{$DIST_SUBDIR}/' 
+make fetch MASTER_SITE_OVERRIDE='file:/cdrom/${DIST_SUBDIR}/' 
 This is equivalent to using CDROM_SITE.
 
 Some common sites have their own variables. It is strongly recommended
@@ -327,4 +330,4 @@
 
 	http://www.openbsd.org/porting.html
 
-$OpenBSD: README,v 1.6 1999/09/26 10:52:55 espie Exp $
+$OpenBSD: README,v 1.9 2001/02/21 23:23:13 avsm Exp $