[BACK]Return to README CVS log [TXT][DIR] Up to [local] / ports

Diff for /ports/README between version 1.8 and 1.9

version 1.8, 1999/10/07 16:44:28 version 1.9, 2001/02/21 23:23:13
Line 17 
Line 17 
 go to ports@openbsd.org  go to ports@openbsd.org
   
 Considering the size of the ports tree, and even though we strive to  Considering the size of the ports tree, and even though we strive to
 eradicate all bugs, things may go wrong on invidual ports.  eradicate all bugs, things may go wrong on individual ports.
 In such a case, as a general rule, try to contact the MAINTAINER first.  In such a case, as a general rule, try to contact the MAINTAINER first.
 If nothing happens after a reasonable delay, start plaguing him,  If nothing happens after a reasonable delay, start plaguing him,
 or go to the next step.  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  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.  Those people can be contacted to put some pressure on a lazy maintainer.
Line 33 
Line 33 
 The ports tree usually live under /usr/ports. It's a hierarchical  The ports tree usually live under /usr/ports. It's a hierarchical
 list of recipes to build various pieces of software.  list of recipes to build various pieces of software.
 We'll call that PORTSDIR in the following discussion.  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  is stored under /usr/ports/infrastructure, INFRA in the following
 discussion.  discussion.
   
Legend:
Removed from v.1.8  
changed lines
  Added in v.1.9