# HG changeset patch
# User Bernhard Herzog <bh@intevation.de>
# Date 1175592288 -7200
# Node ID 225206553bba1fed9868513b5bea14c85c7fd6ce
# Parent  38d66dc6a1e50cb7f461c5602dd5c090240ffc4b
update README part about pbuilder config

diff -r 38d66dc6a1e5 -r 225206553bba README
--- a/README	Mon Apr 02 20:48:25 2007 +0200
+++ b/README	Tue Apr 03 11:24:48 2007 +0200
@@ -75,12 +75,19 @@
 Configure pbuilder
 ~~~~~~~~~~~~~~~~~~
 
-Currently the tree packager assumes that pbuilder has already been set up
-and that the default configuration is suitable for the purposes the tree
-packager instance.  Normally, the default way of setting up sudo should
-be OK.  There is one important interaction with sudo that you need to be
-aware of, though: when the user builder starts pbuilder via sudo,
-pbuilder uses ~builder/.pbuilderrc as its standard configuration file.
+It's best to give the tree packager its own pbuilder configuration and
+directories.  The default configuration uses a "pbuilder" subdirectory
+in /home/builder/enterprise.  If you have created the treepkg.cfg file
+with at least one packager and the correct root_cmd and pbuilderrc
+options (the defaults for both should be OK if you use sudo as described
+above), you can create the directories, the pbuilder configuration and
+the chroot environment with the script initpbuilder.py like this:
+
+   ./initpbuilder.py --mirrorsite=<URL of preferred debian mirror>
+
+You can specify some more mirrors with the --othermirror option.  For
+more information run "./initpbuilder.py --help" and consult the pbuilder
+documentation.
 
 
 Configure the web front-end