[pkgsrc/trunk]: pkgsrc/doc/guide/files Be consistent between sample path and ...

[joerg <joerg%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/76d8a76f16a7
branches:  trunk
changeset: 552658:76d8a76f16a7
user:      joerg <joerg%pkgsrc.org@localhost>
date:      Wed Jan 07 19:59:12 2009 +0000

description:
Be consistent between sample path and bootstrap command.

diffstat:

 doc/guide/files/bulk.xml |  4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diffs (18 lines):

diff -r 90e9ea511bfa -r 76d8a76f16a7 doc/guide/files/bulk.xml
--- a/doc/guide/files/bulk.xml  Wed Jan 07 19:18:25 2009 +0000
+++ b/doc/guide/files/bulk.xml  Wed Jan 07 19:59:12 2009 +0000
@@ -1,4 +1,4 @@
-<!-- $NetBSD: bulk.xml,v 1.3 2008/12/17 09:50:48 rillig Exp $ -->
+<!-- $NetBSD: bulk.xml,v 1.4 2009/01/07 19:59:12 joerg Exp $ -->
 
 <chapter id="bulk">
 <title>Creating binary packages for everything in pkgsrc (bulk
@@ -623,7 +623,7 @@
 <sect2 id="bulk.pbulk.prepare">
 <title>Preparation</title>
 
-<para>First, you need to create a pkgsrc installation for the pbulk infrastructure. No matter on which platform you are (even on NetBSD), you should bootstrap into its own directory. Let's take the 
directory <filename>/usr/pbulk-outer</filename> or <filename>$HOME/pbulk-outer</filename> for it. This installation will be bootstrapped and all the tools that are required for the bulk build will be 
installed there.</para>
+<para>First, you need to create a pkgsrc installation for the pbulk infrastructure. No matter on which platform you are (even on NetBSD), you should bootstrap into its own directory. Let's take the 
directory <filename>/usr/pbulk</filename> or <filename>$HOME/pbulk</filename> for it. This installation will be bootstrapped and all the tools that are required for the bulk build will be installed 
there.</para>
 
 <screen>
 $ <userinput>cd /usr/pkgsrc</userinput>