Mercurial > treepkg
comparison README @ 50:225206553bba
update README part about pbuilder config
author | Bernhard Herzog <bh@intevation.de> |
---|---|
date | Tue, 03 Apr 2007 11:24:48 +0200 |
parents | bad59cd04f34 |
children | b52779523392 |
comparison
equal
deleted
inserted
replaced
49:38d66dc6a1e5 | 50:225206553bba |
---|---|
73 | 73 |
74 | 74 |
75 Configure pbuilder | 75 Configure pbuilder |
76 ~~~~~~~~~~~~~~~~~~ | 76 ~~~~~~~~~~~~~~~~~~ |
77 | 77 |
78 Currently the tree packager assumes that pbuilder has already been set up | 78 It's best to give the tree packager its own pbuilder configuration and |
79 and that the default configuration is suitable for the purposes the tree | 79 directories. The default configuration uses a "pbuilder" subdirectory |
80 packager instance. Normally, the default way of setting up sudo should | 80 in /home/builder/enterprise. If you have created the treepkg.cfg file |
81 be OK. There is one important interaction with sudo that you need to be | 81 with at least one packager and the correct root_cmd and pbuilderrc |
82 aware of, though: when the user builder starts pbuilder via sudo, | 82 options (the defaults for both should be OK if you use sudo as described |
83 pbuilder uses ~builder/.pbuilderrc as its standard configuration file. | 83 above), you can create the directories, the pbuilder configuration and |
84 the chroot environment with the script initpbuilder.py like this: | |
85 | |
86 ./initpbuilder.py --mirrorsite=<URL of preferred debian mirror> | |
87 | |
88 You can specify some more mirrors with the --othermirror option. For | |
89 more information run "./initpbuilder.py --help" and consult the pbuilder | |
90 documentation. | |
84 | 91 |
85 | 92 |
86 Configure the web front-end | 93 Configure the web front-end |
87 ~~~~~~~~~~~~~~~~~~~~~~~~~~~ | 94 ~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
88 | 95 |