thomas: server README.1st,1.107,1.108

cvs at kolab.org cvs at kolab.org
Thu Mar 5 15:27:49 CET 2009


Author: thomas

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

Modified Files:
	README.1st 
Log Message:
README: Moved index generation below upgrade instructions


Index: README.1st
===================================================================
RCS file: /kolabrepository/server/README.1st,v
retrieving revision 1.107
retrieving revision 1.108
diff -u -d -r1.107 -r1.108
--- README.1st	5 Mar 2009 14:24:47 -0000	1.107
+++ README.1st	5 Mar 2009 14:27:47 -0000	1.108
@@ -124,38 +124,6 @@
 # /kolab/bin/openpkg rc all start
 
 
-Generating your own 00INDEX.rdf for installations or upgrades
--------------------------------------------------------------
-
-The source and binary downloads contain the 00INDEX.rdf file needed by
-the "openpkg build" command used by install-kolab.sh to install or upgrade
-a Kolab server.
-
-If you already have your own set of binary packages from a previous build,
-you can use these to create a full binary installer (e.g. to install the
-packages on a second machine) or or a partial binary installer (for upgrades
-where you only want to compile the new .src.rpm files instead of everything).
-
-To generate this file, you always need all .src.rpm files, so link or copy
-them in a new directory (needs to be writable by the kolab user of your
-installation). After this you can link/copy the install-kolab.sh file and
-your binary rpm files (e.g. from /kolab/RPM/PKG/) into this directory and
-run the following command as user kolab or root to create the new
-00INDEX.rdf file:
-
-$ sh install-kolab.sh -X
-
-If you want a pure binary installer, you can remove the .src.rpm files
-now. To be able to use this directory for fresh installations (i.e. not
-only for upgrades), you need to put the OpenPKG bootstrap file
-(openpkg-*.src.sh or openpkg-<ARCH>-<OS>-kolab.rpm) into this directory,
-too.
-
-Index generation tries to cache information about source RPMs in the file
-/kolab/RPM/DB/00INDEX-cache.db, you might want to remove it to save some
-disk space or restore it after new installations to save some time.
-
-
 Upgrade from 2.2.1-beta1 to 2.2.1-rc1
 -------------------------------------
 
@@ -393,6 +361,38 @@
 to be fixed for the final release:
 
 	kolab/issue3438 (kolabFreeBusyPast is not used)
+
+
+Generating your own 00INDEX.rdf for installations or upgrades
+-------------------------------------------------------------
+
+The source and binary downloads contain the 00INDEX.rdf file needed by
+the "openpkg build" command used by install-kolab.sh to install or upgrade
+a Kolab server.
+
+If you already have your own set of binary packages from a previous build,
+you can use these to create a full binary installer (e.g. to install the
+packages on a second machine) or or a partial binary installer (for upgrades
+where you only want to compile the new .src.rpm files instead of everything).
+
+To generate this file, you always need all .src.rpm files, so link or copy
+them in a new directory (needs to be writable by the kolab user of your
+installation). After this you can link/copy the install-kolab.sh file and
+your binary rpm files (e.g. from /kolab/RPM/PKG/) into this directory and
+run the following command as user kolab or root to create the new
+00INDEX.rdf file:
+
+$ sh install-kolab.sh -X
+
+If you want a pure binary installer, you can remove the .src.rpm files
+now. To be able to use this directory for fresh installations (i.e. not
+only for upgrades), you need to put the OpenPKG bootstrap file
+(openpkg-*.src.sh or openpkg-<ARCH>-<OS>-kolab.rpm) into this directory,
+too.
+
+Index generation tries to cache information about source RPMs in the file
+/kolab/RPM/DB/00INDEX-cache.db, you might want to remove it to save some
+disk space or restore it after new installations to save some time.
 
 
 Known problems and workarounds





More information about the commits mailing list