thomas: server release-notes.txt,1.283,1.284 README.1st,1.83,1.84

[cvs at kolab.org]

Author: thomas

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

Modified Files:
	release-notes.txt README.1st 
Log Message:
Update README and release notes.


Index: release-notes.txt
===================================================================
RCS file: /kolabrepository/server/release-notes.txt,v
retrieving revision 1.283
retrieving revision 1.284
diff -u -d -r1.283 -r1.284
--- release-notes.txt	7 Jul 2008 08:16:31 -0000	1.283
+++ release-notes.txt	8 Jul 2008 16:26:16 -0000	1.284
@@ -68,6 +68,13 @@
 
 	Adjusted version number.
 
+	Install fbview-kronolith and horde-kolab-client by default, unless
+	excluded with "-x fbview-kronolith" or "-x horde-kolab-client".
+
+	Removed obsolete options -F/-H/-i.
+
+	kolab/issue2727 (install-kolab.sh: tar uses -O which is not
+	                 implemented in Solaris' tar)
 	kolab/issue2747 (Installation of ix86 binaries fails on amd64 system)
 
     - kolabconf-2.2.0-2008????

Index: README.1st
===================================================================
RCS file: /kolabrepository/server/README.1st,v
retrieving revision 1.83
retrieving revision 1.84
diff -u -d -r1.83 -r1.84
--- README.1st	9 Jun 2008 20:38:53 -0000	1.83
+++ README.1st	8 Jul 2008 16:26:16 -0000	1.84
@@ -33,38 +33,38 @@
 
 You can check the integrity of the downloaded files with:
 
-$ gpg --verify MD5SUMS
+$ gpg --keyserver hkp://subkeys.pgp.net --recv-key 5816791A
+  or import the key from https://www.intevation.de/~thomas/gpg_pub_key.asc
+$ gpg --verify MD5SUMS.sig
 $ md5sum -c MD5SUMS
 
-Then as root, cd into that local (and writable) directory and run
+Then as root, cd into that local directory and run
 
-# ./install-kolab.sh -H -F 2>&1 | tee kolab-install.log
+# ./install-kolab.sh 2>&1 | tee /root/kolab-install.log
 
 to build and install packages in /kolab. The command output will
 be logged to install-kolab.log so that you have a reference in case
 an errors occurs during installation.
 
-The install script needs to be able to write in the current working
-directory, so if you want to keep this directory clean or install
-install packages from a read-only location (e.g. CD-ROM), you can create
-a new directory and pass the path to the packages to the script using
-the -i option, e.g.:
-
-# /media/cdrom/sources/install-kolab.sh -H -F -i /media/cdrom/sources
+The install script needs to store some files and creates a subdirectory
+below /tmp (or $TMPDIR if set) for this purpose.
 
 Horde might create much load on your server if there are many concurrent
-users, so you can choose to not install it by dropping the flag "-H".
+users, so you can choose to not install it by adding the option
+"-x horde-kolab-client" to the call to install-kolab.sh.
 Installing Horde on a separate host is possible, but not discussed here.
 
-If you do not want to install the free/busy view tool, remove the "-F".
+If you do not want to install the free/busy view tool, add the option
+"-x fbview-kronolith".
 
-The binary packages distributed via kolab.org are compiled with -H -F,
-currently you need to compile from the source packages to install without
-these features, see kolab/issue2440 for details.
+The binary packages distributed via kolab.org are compiled with Horde
+and the free/busy view tool. Currently you need to compile from the
+source packages to install without these features, see kolab/issue2440
+for details.
 
 By default, the Kolab server will now be started at boottime, so you
 have to bootstrap the server configuration now to prevent unconfigured
-components from being started.
+components from being started, see kolab/issue1745 for details.
 
 Please run:
 
@@ -93,7 +93,7 @@
 The installation of the new packages works just as for the initial
 installation.  Download the files as described above and run
 
-# ./install-kolab.sh -H -F 2>&1 | tee kolab-update.log
+# ./install-kolab.sh 2>&1 | tee /root/kolab-update.log
 
 If you installed without Horde or F/B-View you need to drop the
 corresponding flags again.
@@ -286,7 +286,7 @@
 
 5.  Start the standard upgrade (as described above):
 
-    # ./install-kolab.sh -H -F 2>&1 | tee kolab-update.log
+    # ./install-kolab.sh 2>&1 | tee /root/kolab-update.log
 
 6.  Before starting the LDAP server the database must be restored from
     the ldif: