diff options
Diffstat (limited to 'encap')
| -rw-r--r-- | encap/INSTALL | 11 |
1 files changed, 7 insertions, 4 deletions
diff --git a/encap/INSTALL b/encap/INSTALL index 1e9209fa7..685b68556 100644 --- a/encap/INSTALL +++ b/encap/INSTALL @@ -74,20 +74,23 @@ unless you ask them to be (via "`REPLACE_CONFIG="yes"; export REPLACE_CONFIG`"). will kick off and background the entire build process. Make output will be redirected to `make.log`, and package build output will go to individual log files. If the entire build is successful, you will see: - {{{### encap build finished...}}} + {{{ + ### encap build finished... + }}} followed by the locations of the various packages at the end of make.log - 1. If everything goes well, try running "`bcfg2-repo-validate`". This should - not generate a python traceback, but will probably throw an error. Packages that you can install on other machines will be in the "`DIST`" directory. In most cases you will only need the self-extracting/installing package with the name like "`bcfg2-*.run`"; that will install the bcfg2 client. +You will need to install this even on your build machine(s) and server(s), so +the setup script will run. You can install the doc packages if you want, although it probably makes more sense to let bcfg2 install them on machines you want to have them on after you get stuff up and running. -On GNU/Linux platforms, glib and gamin will also be built; these only have to be installed only on the bcfg2 server machine. +On GNU/Linux platforms, glib and gamin will also be built; these only have to +be installed only on the bcfg2 server machine. Cheetah will be built on all platforms (as it is needed as a build-time prerequisite), however for run-time it only needs to be installed on the bcfg2 |