Changes between Version 1 and Version 2 of EncapInstall

Timestamp:

09/05/06 11:17:07 (15 years ago)

Author:

dclark

Comment:

--

EncapInstall

@@ -12 +12 @@
      running "`ksh -f values.c`" as root (or openssl will segfault)
  * GNU make (make sure "gmake" links to GNU make on non-GNU platforms)
- * /usr/local/man should be a directory, not a symbolic link
  * epkg (the encap package manager)
    * Canonical website is http://www.encap.org/epkg
@@ -76 +75 @@
     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
@@ -89 +90 @@
 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 
@@ -100 +102 @@
 
 == Documentation Version ==
- * This is a copy of: $Id: INSTALL 2173 2006-09-02 23:37:24Z dclark $
+ * This is a copy of: $Id: INSTALL 2187 2006-09-04 18:12:44Z dclark $
  * Most recent version: http://www.bcfg2.org/browser/trunk/bcfg2/encap/INSTALL