summaryrefslogtreecommitdiff
path: root/doc/guide
diff options
context:
space:
mode:
authorrillig <rillig>2007-07-20 15:18:46 +0000
committerrillig <rillig>2007-07-20 15:18:46 +0000
commitf54e9f086a2a54da45115514ed454dcb1fe7b70b (patch)
treeadf3627cbfb00820b3ee34fbed677f0c025fedb3 /doc/guide
parent142e9fcd9ad8d54f371ca7c4fbb05fae174f09d3 (diff)
downloadpkgsrc-f54e9f086a2a54da45115514ed454dcb1fe7b70b.tar.gz
Added a recommended .cvsrc file.
Diffstat (limited to 'doc/guide')
-rw-r--r--doc/guide/files/getting.xml21
1 files changed, 20 insertions, 1 deletions
diff --git a/doc/guide/files/getting.xml b/doc/guide/files/getting.xml
index 937150005ad..858407b4b6e 100644
--- a/doc/guide/files/getting.xml
+++ b/doc/guide/files/getting.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: getting.xml,v 1.19 2007/06/01 11:07:25 rillig Exp $ -->
+<!-- $NetBSD: getting.xml,v 1.20 2007/07/20 15:18:46 rillig Exp $ -->
<chapter id="getting">
<title>Where to get pkgsrc and how to keep it up-to-date</title>
@@ -89,6 +89,25 @@ release=pkgsrc
&uprompt; <userinput>export CVSROOT CVS_RSH</userinput>
</screen>
+ <para>By default, cvs doesn't do things like most people would
+ expect it to do, and this is unlikely to change. But there is a
+ way to convince cvs, by creating a file called
+ <filename>.cvsrc</filename> in your home directory and saving
+ the following lines to it. This file will save you lots of
+ headache and some bug reports, so we strongly recommend it. You
+ can find an explanation of this file in the CVS
+ documentation.</para>
+
+<programlisting>
+# recommended CVS configuration file from the pkgsrc guide
+checkout -P
+update -d
+release -d
+diff -up
+cvs -q -z3
+rdiff -u
+</programlisting>
+
<para>Then, you change to the directory where you want to have
your copy of pkgsrc. In most cases this is
<filename>/usr</filename>. In that directory you run the