OpenPKG CVS Repository
http://cvs.openpkg.org/
____________________________________________________________________________
Server: cvs.openpkg.org Name: Thomas Lotterer
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-re Date: 20-Oct-2004 16:22:31
Branch: HEAD Handle: 2004102015223000
Modified files:
openpkg-re upgrade.txt
Log:
Typical practice upgrading to a new OpenPKG RELEASE
Summary:
Revision Changes Path
1.49 +66 -5 openpkg-re/upgrade.txt
____________________________________________________________________________
patch -p0 <<'@@ .'
Index: openpkg-re/upgrade.txt
============================================================================
$ cvs diff -u -r1.48 -r1.49 upgrade.txt
--- openpkg-re/upgrade.txt 20 Jul 2004 08:00:16 -0000 1.48
+++ openpkg-re/upgrade.txt 20 Oct 2004 14:22:30 -0000 1.49
@@ -2,11 +2,72 @@
General Notes
=============
- o $Revision: 1.48 $. The most recent update of this file can be
+ o $Revision: 1.49 $. The most recent update of this file can be
downloaded from http://cvs.openpkg.org/openpkg-re/upgrade.txt
- o This file upgrade.txt file talked about tweaks and quirks when
- upgrading, common pitfalls and ways to bypass them. It was replaced
- by the new "Release Notes" document which can be downloaded from
- http://cvs.openpkg.org/openpkg-re/releasenotes.txt
+ Typical practice upgrading to a new OpenPKG RELEASE
+ ===================================================
+
+ o Information
+
+ Become familiar with the vendor documentation of your favorite
+ applications and the OpenPKG release notes. The latter can be
+ downloaded from http://cvs.openpkg.org/openpkg-re/releasenotes.txt.
+
+ o Backup
+
+ Backup your data and configuration. The new release might ship a new
+ incompatible vendor version of your favorite application. In the
+ worst case it might render your data invalid when running it against
+ old data without proper conversion. On installation of binaries
+ OpenPKG rpm might move your configuration files away into backup
+ files named with .rpmsave suffix. This means your customization is
+ gone and the application reverts to the OpenPKG default. Existence
+ of such backup files inhibits daemons from getting started. You must
+ manually merge or copy back your customization and get rid of the
+ backup files.
+
+ WARNING: when remotely upgrading OpenPKG's "openssh" package make
+ sure you do not leave the shell unless you ensured it did
+ not revert to default behavior which includes deadly denial
+ of root login and listening to local address only.
+
+ o OpenPKG (bootstrap)
+
+ Rebuild the new "openpkg" (bootstrap) package using the existing
+ one. Something like
+
+ $ $PREFIX/bin/openpkg rpm --rebuild \
+ ftp://ftp.openpkg.org/release/2.2/SRC/openpkg-2.2.0-2.2.0.src.rpm
+
+ will do the job, then install the resulting binary using
+
+ $ $PREFIX/bin/openpkg rpm -Uvh openpkg-2.2.0-2.2.0.*-*.rpm
+
+ o Devtools
+
+ Upgrade the development tools. Start with "make", "binutils" and "gcc".
+
+ o Build
+
+ Install "perl" and "openpkg-tools". This enables the "openpkg build"
+ command. Use it to compute a shell script formatted list of rebuild
+ and install action pairs ordered by dependency requirements and
+ annotated with optional defines you used to create the existing
+ installation.
+
+ $ $PREFIX/bin/openpkg build -Ua | tee todo.sh
+
+ Review this script. It is a good idea to move all the worthy
+ applications, the ones you actually use OpenPKG for and not their
+ dependencies, to the end of the script and deactivate their
+ installation by commenting out parts of the script. You can run
+ the build of all packages and the installation of dependency tools
+ unattended. This might take hours.
+
+ o Finalize
+
+ Come back later and run the installation of the worthy applications
+ manually. Watch for ".rpmsaves", resolve them and restart the
+ daemons.
@@ .
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
