[BACK]Return to 33.html CVS log [TXT][DIR] Up to [local] / www

Diff for /www/33.html between version 1.56 and 1.57

version 1.56, 2019/06/12 20:57:16 version 1.57, 2019/06/13 05:33:57
Line 390 
Line 390 
 <h3>Ports Tree</h3>  <h3>Ports Tree</h3>
 <p>  <p>
 A ports tree archive is also provided.  To extract:  A ports tree archive is also provided.  To extract:
 <p>  
 <blockquote><pre>  <blockquote><pre>
 # <kbd>cd /usr</kbd>  # <kbd>cd /usr</kbd>
 # <kbd>tar xvfz /tmp/ports.tar.gz</kbd>  # <kbd>tar xvfz /tmp/ports.tar.gz</kbd>
Line 410 
Line 409 
 on most architectures (over 2000 packages build on i386, for instance).  on most architectures (over 2000 packages build on i386, for instance).
 <p>  <p>
 The <i>ports/</i> directory represents a CVS (see the manpage for  The <i>ports/</i> directory represents a CVS (see the manpage for
 <a href="https://man.openbsd.org/cvs.1">  <a href="https://man.openbsd.org/cvs.1">cvs(1)</a> if
 cvs(1)</a> if  
 you aren't familiar with CVS) checkout of our ports.  As with our complete  you aren't familiar with CVS) checkout of our ports.  As with our complete
 source tree, our ports tree is available via anoncvs.  So, in  source tree, our ports tree is available via anoncvs.  So, in
 order to keep current with it, you must make the <i>ports/</i> tree  order to keep current with it, you must make the <i>ports/</i> tree
 available on a read-write medium and update the tree with a command  available on a read-write medium and update the tree with a command
 like:  like:
 <p>  
 <blockquote><pre>  <blockquote><pre>
 # <kbd>cd [portsdir]/; cvs -d anoncvs@server.openbsd.org:/cvs update -Pd -rOPENBSD_3_3</kbd>  # <kbd>cd [portsdir]/; cvs -d anoncvs@server.openbsd.org:/cvs update -Pd -rOPENBSD_3_3</kbd>
 </pre></blockquote>  </pre></blockquote>
Legend:
Removed from v.1.56  
changed lines
  Added in v.1.57