kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Suggest simple way first, avoid tinkering at CVS_RSH, when it's not needed.

Browse source
This commit is contained in:
asau 2011-06-02 06:45:49 +00:00
parent 73d502b8a0
commit becf54194b
1 changed files with 9 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
doc/guide/files/getting.xml
View file

@ -1,4 +1,4 @@
<!-- $NetBSD: getting.xml,v 1.27 2010/12/23 10:42:16 asau Exp $ -->
<!-- $NetBSD: getting.xml,v 1.28 2011/06/02 06:45:49 asau Exp $ -->
<chapter id="getting">
<title>Where to get pkgsrc and how to keep it up-to-date</title>
@ -164,12 +164,15 @@ release -d
<sect2 id="uptodate-cvs">
<title>Via CVS</title>
<para>To update pkgsrc via CVS, make sure the environment
variable <varname>CVS_RSH</varname> is set as above. Then,
change to the <filename>pkgsrc</filename> directory and run cvs:</para>
<para>To update pkgsrc via CVS, change to the <filename>pkgsrc</filename> directory and run cvs:</para>
<screen>&uprompt; <userinput>cd /usr/pkgsrc</userinput>
&uprompt; <userinput>cvs update -dP</userinput></screen>
<screen>&uprompt; <userinput>cd /usr/pkgsrc &amp;&amp; cvs update -dP</userinput>
</screen>
<para>If you get error messages from <literal>rsh</literal>, you need to set CVS_RSH variable as described above. E.g.:</para>
<screen>&uprompt; <userinput>cd /usr/pkgsrc &amp;&amp; env CVS_RSH=ssh cvs up -dP</userinput>
</screen>
<sect3 id="uptodate-cvs-switch">
<title>Switching between different pkgsrc branches</title>