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

Diff for /www/anoncvs.html between version 1.463 and 1.464

version 1.463, 2016/09/09 14:31:25 version 1.464, 2016/09/20 01:01:12
Line 12 
Line 12 
 <link rel="stylesheet" type="text/css" href="openbsd.css">  <link rel="stylesheet" type="text/css" href="openbsd.css">
 <link rel="canonical" href="https://www.openbsd.org/anoncvs.html">  <link rel="canonical" href="https://www.openbsd.org/anoncvs.html">
 <style type="text/css">  <style type="text/css">
   h3 { color: #0000e0; }    h3, h4 { color: #0000e0; }
 </style>  </style>
 </head>  </head>
   
Line 89 
Line 89 
 # <b>tar xzf /tmp/ports.tar.gz</b>  # <b>tar xzf /tmp/ports.tar.gz</b>
 </pre></blockquote>  </pre></blockquote>
   
 <h3 id="using">Using CVS to get and update your source tree</h3>  <h3 id="using">Using CVS to get and update your source trees</h3>
   
 CVS was designed to be a simple way to retrieve and update your sources.  <a href="http://man.openbsd.org/cvs">cvs(1)</a> was designed to be a simple way
   to retrieve and update your sources.
 You must first decide whether you want to track <i>-current</i> or a  You must first decide whether you want to track <i>-current</i> or a
 <a href="stable.html">patch branch</a>.  <a href="stable.html">patch branch</a>.
 The current tree has all of the up to the minute changes,  The current tree has all of the up to the minute changes,
Line 106 
Line 107 
 If you begin with <tt>src.tar.gz</tt> and <tt>sys.tar.gz</tt> as mentioned  If you begin with <tt>src.tar.gz</tt> and <tt>sys.tar.gz</tt> as mentioned
 above, you can skip the initial <tt>get</tt> and proceed to updating.  above, you can skip the initial <tt>get</tt> and proceed to updating.
   
 <ul>  
 <li>First, start out by getting an initial tree (the following commands assume  
 that your user is member of the <tt>wsrc</tt> group):  
   
 <p>  <p>
   <b>Warning:</b>
   When using cvs, you should take care that your current directory is either the
   root of the tree you are referencing or in a separate place such as
   <tt>/tmp</tt>.
   Some commands, such as <tt>cvs get</tt>, can create an arbitrary sub-tree in the
   current directory, and a subsequent update will recursively flesh out this
   sub-tree.
   
   <h4>Getting an initial tree</h4>
   
   The following commands assume that your user is member of the <tt>wsrc</tt>
   group:
   
   <p>
 If you are following <i>current</i>:  If you are following <i>current</i>:
   
 <blockquote><pre>  <blockquote><pre>
Line 145 
Line 157 
   
 <blockquote><pre>  <blockquote><pre>
 Are you sure you want to continue connecting (yes/no)? <b>yes</b>  Are you sure you want to continue connecting (yes/no)? <b>yes</b>
 Warning: Permanently added 'anoncvs.spacehopper.org' (ED25519) to the list of known hosts.</b>  Warning: Permanently added 'anoncvs.spacehopper.org' (ED25519) to the list of known hosts.
 </pre></blockquote>  </pre></blockquote>
   
 <li> Any time afterwards, to update this tree:  <h4>Updating an existing tree</h4>
   
 <p>  
 If you are following <i>current</i>:  If you are following <i>current</i>:
   
 <blockquote><pre>  <blockquote><pre>
Line 169 
Line 180 
 It would not destroy any of your local changes; rather it would attempt  It would not destroy any of your local changes; rather it would attempt
 to merge changes in.  to merge changes in.
   
 <p>  <h4>Changing the server</h4>
 <li> NOTE:  
 If you are updating a source tree that you initially fetched  If you are updating a source tree that you initially fetched
 from a different server, or from a tar file, you <b>must</b>  from a different server, or from a tar file, you <b>must</b>
 add the <em>-d [cvsroot]</em> option to cvs.  add the <em>-d [cvsroot]</em> option to cvs.
Line 179 
Line 190 
 $ <b>cd /usr/src</b>  $ <b>cd /usr/src</b>
 $ <b>cvs -d anoncvs@anoncvs.ca.openbsd.org:/cvs -q up -Pd</b>  $ <b>cvs -d anoncvs@anoncvs.ca.openbsd.org:/cvs -q up -Pd</b>
 </pre></blockquote>  </pre></blockquote>
 </ul>  
   
 To <a name="ports">use</a> <a href="faq/ports">ports</a>, it is similar to src.  <h4>Getting the ports and xenocara trees</h4>
   
 Make sure your user is member of the <tt>wsrc</tt> group and that  Make sure your user is member of the <tt>wsrc</tt> group and that
 <tt>/usr/ports</tt> is group writable by <tt>wsrc</tt>.  <tt>/usr/ports</tt> is group writable by <tt>wsrc</tt>.
   Replace <tt>ports</tt> with <tt>xenocara</tt> throughout to get or update a
   xenocara tree.
   
 <ul><li>  <ul><li>
   
Line 225 
Line 238 
 cvs' output.  cvs' output.
 For those who like to see screenfulls of output, it can be omitted.  For those who like to see screenfulls of output, it can be omitted.
   
 <p>  <h4>Creating a diff</h4>
 To make a diff of a locally patched module (here <i>cd.c</i>) to include with  
   To make a diff of a locally patched module (here <tt>cd.c</tt>) to include with
 a bug report:  a bug report:
   
 <blockquote><pre>  <blockquote><pre>
 $ <b>cd /usr</b>  $ <b>cd /usr</b>
 $ <b>cvs diff -u src/sys/scsi/cd.c &gt; /tmp/patch</b>  $ <b>cvs diff -u src/sys/scsi/cd.c &gt; /tmp/patch</b>
 </pre></blockquote>  </pre></blockquote>
   
 The <a href="http://man.openbsd.org/cvs">cvs(1)</a> man page  
 (included with the CVS sources) has much more  
 information about how CVS can be used.  
   
 <p>  
 <b>Warning:</b>  
 When using cvs, you should take care that your current directory is either  
 the root of the tree you are referencing or in a separate place such as  
 <tt>/tmp</tt>.  
 Some commands such as "get" can create an arbitrary sub-tree in the current  
 directory, and a subsequent update will recursively flesh out this sub-tree.  
   
 <h3 id="EXAMPLE">Example usage for cvs(1)</h3>  <h3 id="EXAMPLE">Example usage for cvs(1)</h3>
   

Legend:
Removed from v.1.463  
changed lines
  Added in v.1.464