gunnar: server README.1st,1.59,1.60 README.webclient,1.7,NONE

cvs at kolab.org cvs at kolab.org
Fri Oct 19 11:06:44 CEST 2007


Author: gunnar

Update of /kolabrepository/server
In directory doto:/tmp/cvs-serv9415

Modified Files:
	README.1st 
Removed Files:
	README.webclient 
Log Message:
Update instructions.

Index: README.1st
===================================================================
RCS file: /kolabrepository/server/README.1st,v
retrieving revision 1.59
retrieving revision 1.60
diff -u -d -r1.59 -r1.60
--- README.1st	15 Jun 2007 13:11:17 -0000	1.59
+++ README.1st	19 Oct 2007 09:06:41 -0000	1.60
@@ -31,9 +31,19 @@
 
 Then as root, cd into that local directory and run
 
-# sh obmtool kolab 2>&1 | tee kolab-build.log
+# ./install-kolab.sh 2>&1 | tee kolab-build.log
+
+to build and install packages in /kolab. The command output will
+be logged to kolab-build.log so that you have a reference in case
+an errors occurs during installation.
+
+If you wish to include the Horde groupware client and/or the Free/Busy
+view tool in you installation, you need to append the flag(s) "-H"
+and/or "-F". The following installs the server including Horde and
+F/B-View:
+
+# ./install-kolab.sh -H -F 2>&1 | tee kolab-build.log
 
-to build and install packages in /kolab.
 By default, the Kolab Server will now be started at boottime.
 After the build/install is complete, please run
 
@@ -59,15 +69,20 @@
 The installation of the new packages works just as for the initial
 installation.  Download the files as described above and run
 
-# sh obmtool kolab 2>&1 | tee kolab-update.log
+# ./install-kolab.sh 2>&1 | tee kolab-update.log
 
-obmtool will usually automatically determine which packages need to be
-built.  If you have made changes to configuration files or an updated
-package includes configuration files which are usually regenerated from
-files in /kolab/etc/kolab/templates/ the old configuration file will be
-saved with the extension .rpmsave.  For files generated from templates
-you just have to remove the rpmsave file, because services will refuse
-to start if there still is an rpmsave file, e.g.:
+If you installed with Horde or F/B-View you need to run
+
+# ./install-kolab.sh -H -F 2>&1 | tee kolab-update.log
+
+install-kolab.sh will usually automatically determine which packages
+need to be built.  If you have made changes to configuration files or
+an updated package includes configuration files which are usually
+regenerated from files in /kolab/etc/kolab/templates/ the old
+configuration file will be saved with the extension .rpmsave.  For
+files generated from templates you just have to remove the rpmsave
+file, because services will refuse to start if there still is an
+rpmsave file, e.g.:
 
 # rm /kolab/etc/clamav/*.conf.rpmsave
 

--- README.webclient DELETED ---





More information about the commits mailing list