Mercurial > treepkg
comparison README @ 71:2eefd12526ff
flesh out the REAME file some more
| author | Bernhard Herzog <bh@intevation.de> |
|---|---|
| date | Thu, 12 Apr 2007 21:43:14 +0200 |
| parents | 4b537aadc5ce |
| children | 7e6da00cccef |
comparison
equal
deleted
inserted
replaced
| 70:4b537aadc5ce | 71:2eefd12526ff |
|---|---|
| 66 ~~~~~~~~~~~~~~~~~~~~~~ | 66 ~~~~~~~~~~~~~~~~~~~~~~ |
| 67 | 67 |
| 68 The file demo.cfg contains example configuration that contains most of | 68 The file demo.cfg contains example configuration that contains most of |
| 69 what is needed to package KDEPIM and kde-i18n from the KDEPIM enterprise | 69 what is needed to package KDEPIM and kde-i18n from the KDEPIM enterprise |
| 70 branch. Copy this file to treepkg.cfg and adapt it to your needs. The | 70 branch. Copy this file to treepkg.cfg and adapt it to your needs. The |
| 71 comments in the file should provide enough hints to get you started. | 71 comments in the file should provide most of the hints to get you |
| 72 started. Some more information is in the "Configuring a packager" | |
| 73 section below. | |
| 74 | |
| 75 | |
| 76 Configuring a packager | |
| 77 ~~~~~~~~~~~~~~~~~~~~~~ | |
| 78 | |
| 79 The configuration file contains on section for each packager. The | |
| 80 section name starts with a "pkg_" prefix. The possible options are | |
| 81 described in demo.cfg. However there are some things that need to be | |
| 82 set up outside of the config file. | |
| 83 | |
| 84 Each packager has a base directory (the base_dir option in the | |
| 85 corresponding pkg_-section). One thing needed by a packager is the | |
| 86 contents of the debian subdirectory of the debian source package. When | |
| 87 creating the source package, the packager simply copies the subdirectory | |
| 88 "debian" of the base_dir into the directory making up the source tree. | |
| 89 How the debian directory is created and maintained is up to you. | |
| 90 Usually it's a good idea to start with the debian subdirectory an | |
| 91 existing debian package for the software. | |
| 72 | 92 |
| 73 | 93 |
| 74 Configure pbuilder | 94 Configure pbuilder |
| 75 ~~~~~~~~~~~~~~~~~~ | 95 ~~~~~~~~~~~~~~~~~~ |
| 76 | 96 |
| 120 The config file for publishstaticweb.py is demostaticweb.cfg. Copy this | 140 The config file for publishstaticweb.py is demostaticweb.cfg. Copy this |
| 121 file to ststaticweb.cfg and adapt it to your system. The comments in | 141 file to ststaticweb.cfg and adapt it to your system. The comments in |
| 122 the file describe the options. Afterwards, run the script with | 142 the file describe the options. Afterwards, run the script with |
| 123 | 143 |
| 124 ./publishstaticweb.py | 144 ./publishstaticweb.py |
| 145 | |
| 146 | |
| 147 Running the Tree Packager | |
| 148 ------------------------- | |
| 149 | |
| 150 After configuration, run the tree packager with | |
| 151 | |
| 152 ./runtreepkg.py [options] [packager...] | |
| 153 | |
| 154 For each packager listed on the command line -- or all configured | |
| 155 packagers if none are given -- the tree packager checks our or updates | |
| 156 the sources and builds binary packages if the new revision hasn't been | |
| 157 packaged yet. | |
| 158 | |
| 159 If the option --once has been given, the tree packager exits after it | |
| 160 has checked each packager once. Without it, the check is done | |
| 161 repeatedly. The interval between two checks can be set in the config | |
| 162 file. | |
| 163 | |
| 164 Call runtreepkg.py with the --help option to see a list of the available | |
| 165 options. |