Outline for RPM and AutoRPM based Upgrade Presentation to COLUG 02/26/2000.
Presented by Phil Hunter <hunter@owlriver.com>
  1. RPM Introduction
  2. Reference materials - primary sources

  3. Why
    Note: Red Hat itself, in its CD based upgrades does NOT honor the principle of not using the --force option. This is probably in the interest of avoiding support load. Their disk based upgrade procedure requires a reboot, from CD or floppy.

    Owl River Company [ORC] technical support is the most 'vocal' advocate of 'hot box' upgrades on the RPM-list. The presentation today is representative of support approach of ORC, which is initially more 'expensive' in terms of sysadmin time, but MUCH more 'correct' to RPM design goals. The 'payback' of such an approach is that the proprietary ORC host management tools will thereafter manage 'by exception' the day-to-day host task supervision load in a production environment.

  4. Competing approaches

  5. Third party documents - secondary sources

(This section added 000804)
------------------------------------------
cookbook:  (clip and save) 

to rebuild a SRPM on a local machine:


    cd /usr/src
#          (A convenient place to stash unbuilt SRPMs)
    rpm -Uvh fetchmail-5.4.4-1.src.rpm
    rpmbuild -ba /usr/src/redhat/SPECS/fetchmail{-hit TAB key-}   
#          (It builds)   
#          (Note where the result is)
    rpm -Uvh /usr/src/redhat/RPMS/i386.fetchmail-5.4.4-1.rpm   



(http://www.colug.net/notes/0002mtg/show.php3?file=RPM_UG_outline.html)
init. 000228 -- Phil Hunter -- Copyright (c) 2000 All rights reserved. hunter@owlriver.com last rev. 020502