OpenPKG CVS Repository
  http://cvs.openpkg.org/
  ____________________________________________________________________________

  Server: cvs.openpkg.org                  Name:   Thomas Lotterer
  Root:   /v/openpkg/cvs                   Email:  [EMAIL PROTECTED]
  Module: openpkg-re                       Date:   27-Jun-2006 21:11:40
  Branch: HEAD                             Handle: 2006062720114000

  Modified files:
    openpkg-re              releasenotes.txt

  Log:
    Recommended Upgrade procedure from any OpenPKG-2.x-RELEASE

  Summary:
    Revision    Changes     Path
    1.22        +55 -1      openpkg-re/releasenotes.txt
  ____________________________________________________________________________

  patch -p0 <<'@@ .'
  Index: openpkg-re/releasenotes.txt
  ============================================================================
  $ cvs diff -u -r1.21 -r1.22 releasenotes.txt
  --- openpkg-re/releasenotes.txt       22 Jun 2006 19:19:08 -0000      1.21
  +++ openpkg-re/releasenotes.txt       27 Jun 2006 19:11:40 -0000      1.22
  @@ -2,7 +2,7 @@
     OpenPKG Release Notes
     =====================
   
  -  o $Revision: 1.21 $. The most recent update of this file can be
  +  o $Revision: 1.22 $. The most recent update of this file can be
       downloaded from http://cvs.openpkg.org/openpkg-re/releasenotes.txt
       The history of this document, specific versions and
       differences between versions can be retrieved from
  @@ -118,6 +118,60 @@
       an alternate package download location, usually a local mirror of -
       probably modified - packages. See "openpkg man release".
   
  +  o Recommended Upgrade procedure from any OpenPKG-2.x-RELEASE
  +
  +    The steps below assume you work as m_usr and become root by means of 
sudo.
  +    Please adjust if you use another mechanism to gain higher privileges or
  +    simplify if you work as root all the time.
  +
  +    1# su - m_usr
  +    2$ openpkg rpm --rebuild 
ftp://ftp.openpkg.org/stable/2.20060622/SRC/openpkg-2.20060622-2.20060622.src.rpm
  +    3$ MY/sudo $HOME/bin/openpkg rpm -Uvh 
$HOME/RPM/PKG/openpkg-2.20060622-2.20060622.*-*-*.rpm
  +    4$ openpkg rpm -e openpkg-tools openpkg-registry
  +    5$ #optional echo "TAG=2-STABLE-20060622" >$HOME/etc/openpkg/release
  +    6$ openpkg register --mode=post [EMAIL PROTECTED]
  +    7$ openpkg build openpkg-tools | sh
  +    8$ openpkg build -P MY/sudo -ZaKB | sh
  +
  +    1   switch to the administrative user environment. The m_usr is a good 
choice
  +        and assumed in this example having HOME set to the instance prefix.  
You
  +        can omit this step if you work as superuser all the time.
  +
  +    2   fetch and rebuild the bootstrap. The example shows the snapshotted 
version
  +        which works verbatim. You might find an update in the UPD folder 
beneath
  +        SRC. Or climb up the STABLE branch looking into
  +        ftp://ftp.openpkg.org/stable/2/.
  +
  +    3   update the bootstrap. The example shows sudo in action and assumes 
the
  +        sudoers file has been configured in advance, allowing m_usr to 
execute
  +        $HOME/bin/openpkg as superuser.
  +
  +    4   remove openpkg-tools and openpkg-registry. The bootstrap contains a
  +        "openpkg build" simulator which is able to download new tools.  The
  +        registry client is completely embedded in new bootstraps.
  +
  +    5   by default, "openpkg build" will look for the latest packages in the
  +        branch most appropriate for your bootstrap: CURRENT, STABLE or
  +        SOLID/RELEASE.  If you want to stay close to the snapshot and not 
follow
  +        the STABLE branch then tell the tool to stay on a certain TAG. This 
is a
  +        completely optional step.
  +
  +    6   register the instance, of course replacing the user data with the 
ones you
  +        used previously to enroll an account on 
http://registry.openpkg.org/. The
  +        easiest way is to use the post mode, which requires a working HTTP
  +        connection to be established from the instance to the registry. If 
this is
  +        not possible or allowed, use --mode=fake and copy'n'paste the 
registration
  +        data into the registry drop-xml form. Do not forget to login into the
  +        registry and associate the instance with your account. Otherwise 
downloads
  +        will not work.
  +
  +    7   run the "openpkg build" simulator which will download, rebuild and 
install
  +        "make", "binutils", "gcc", "perl" and "openpkg-tools". After that 
step the
  +        "openpkg build" command is full featured.
  +
  +    8   use the full feature "openpkg build" command to upgrade all 
packages. Note
  +        that the "-Za" combination is new in openpkg-tools-0.8.59
  +
     Upgrade from OpenPKG-2.5-RELEASE to OpenPKG-2-STABLE-20060622
     =============================================================
   
  @@ .
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
CVS Repository Commit List                     [email protected]

Reply via email to