Upgrade Notes
  =============

  o $Revision: 1.54 $. The most recent update of this file can be
    downloaded from http://cvs.openpkg.org/openpkg-re/upgrade.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 Cleanup

    Building OpenPKG requires approximately 300MB of disk space on the
    filesystem holding the source and temporary areas. Some packages
    are known to use an equal amount of space during build like gcc,
    some have even larger requirements like mozilla and qt. Unless RPM
    macros %_sourcedir, %_specdir, %_builddir and %_tmppath have been
    overridden the default place is $PREFIX/RPM/SRC and $PREFIX/RPM/TMP.
    Assuming you use these places in their intended form it is safe to
    delete all data from them to cleanup relicts from previous rebuilds.

  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.4/SRC/openpkg-2.4.0-2.4.0.src.rpm

    will do the job, then install the resulting binary using

        $ $PREFIX/bin/openpkg rpm -Uvh \
          $PREFIX/RPM/PKG/openpkg-2.4.0-2.4.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.