Mercurial > treepkg
diff README @ 72:7e6da00cccef
fix typos in README
author | Bernhard Herzog <bh@intevation.de> |
---|---|
date | Thu, 12 Apr 2007 21:44:47 +0200 |
parents | 2eefd12526ff |
children | 26a617c0f76b |
line wrap: on
line diff
--- a/README Thu Apr 12 21:43:14 2007 +0200 +++ b/README Thu Apr 12 21:44:47 2007 +0200 @@ -83,19 +83,19 @@ Each packager has a base directory (the base_dir option in the corresponding pkg_-section). One thing needed by a packager is the -contents of the debian subdirectory of the debian source package. When -creating the source package, the packager simply copies the subdirectory -"debian" of the base_dir into the directory making up the source tree. -How the debian directory is created and maintained is up to you. -Usually it's a good idea to start with the debian subdirectory an -existing debian package for the software. +contents of the debian sub-directory of the debian source package. When +creating the source package, the packager simply copies the +sub-directory "debian" of the base_dir into the directory making up the +source tree. How the debian directory is created and maintained is up +to you. Usually it's a good idea to start with the debian sub-directory +an existing debian package for the software. Configure pbuilder ~~~~~~~~~~~~~~~~~~ It's best to give the tree packager its own pbuilder configuration and -directories. The default configuration uses a "pbuilder" subdirectory +directories. The default configuration uses a "pbuilder" sub-directory 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 @@ -118,7 +118,7 @@ web-page or as a directory with a bunch of files making up a static web-site. -Webserver: +Web-server: The default configuration should be OK in most cases. If you want you can customize it in cherrypy.cfg. Start the web front-end with @@ -138,8 +138,8 @@ packager host to a third host. The config file for publishstaticweb.py is demostaticweb.cfg. Copy this -file to ststaticweb.cfg and adapt it to your system. The comments in -the file describe the options. Afterwards, run the script with +file to staticweb.cfg and adapt it to your system. The comments in the +file describe the options. Afterwards, run the script with ./publishstaticweb.py