head	1.26;
access;
symbols;
locks; strict;
comment	@# @;


1.26
date	2005.08.10.13.13.42;	author thl;	state Exp;
branches;
next	1.25;

1.25
date	2004.02.25.09.23.57;	author thl;	state Exp;
branches;
next	1.24;

1.24
date	2002.03.21.20.50.44;	author rse;	state Exp;
branches;
next	1.23;

1.23
date	2002.02.24.20.15.12;	author rse;	state Exp;
branches;
next	1.22;

1.22
date	2002.02.22.13.16.28;	author ms;	state Exp;
branches;
next	1.21;

1.21
date	2002.02.20.10.49.30;	author ms;	state Exp;
branches;
next	1.20;

1.20
date	2001.12.17.15.33.25;	author rse;	state Exp;
branches;
next	1.19;

1.19
date	2001.12.17.15.22.21;	author rse;	state Exp;
branches;
next	1.18;

1.18
date	2001.11.07.15.52.28;	author ms;	state Exp;
branches;
next	1.17;

1.17
date	2001.11.05.17.54.10;	author ms;	state Exp;
branches;
next	1.16;

1.16
date	2001.10.28.15.14.10;	author rse;	state Exp;
branches;
next	1.15;

1.15
date	2001.10.10.10.42.08;	author ms;	state Exp;
branches;
next	1.14;

1.14
date	2001.09.18.14.32.24;	author ms;	state Exp;
branches;
next	1.13;

1.13
date	2001.09.17.13.29.01;	author rse;	state Exp;
branches;
next	1.12;

1.12
date	2001.09.10.14.26.42;	author rse;	state Exp;
branches;
next	1.11;

1.11
date	2001.09.05.14.19.18;	author ms;	state Exp;
branches;
next	1.10;

1.10
date	2001.09.01.13.43.18;	author rse;	state Exp;
branches;
next	1.9;

1.9
date	2001.08.30.15.03.18;	author ms;	state Exp;
branches;
next	1.8;

1.8
date	2001.08.30.12.58.54;	author rse;	state Exp;
branches;
next	1.7;

1.7
date	2001.08.30.07.49.36;	author thl;	state Exp;
branches;
next	1.6;

1.6
date	2001.08.30.07.37.30;	author thl;	state Exp;
branches;
next	1.5;

1.5
date	2001.08.30.07.31.31;	author thl;	state Exp;
branches;
next	1.4;

1.4
date	2001.08.30.07.29.59;	author thl;	state Exp;
branches;
next	1.3;

1.3
date	2001.08.30.07.20.59;	author thl;	state Exp;
branches;
next	1.2;

1.2
date	2001.08.29.13.51.36;	author thl;	state Exp;
branches;
next	1.1;

1.1
date	2001.08.28.13.04.04;	author rse;	state Exp;
branches;
next	;


desc
@@


1.26
log
@mention openpkg-tools in quickref
@
text
@
  OpenPKG Quick Reference 
  =======================

  Legend: "$"   : shell prompt of any non-root user
          "#"   : shell prompt of root user
          "<x>" : variable text; to be substituted suitable according to context

  o Global decision on OpenPKG filesystem path and user/group ID:

    All the following steps assume a permanent and unchanging filesystem path
    to OpenPKG and all its subsequently installed software packages.  Choose
    the OpenPKG path and user/group ID carefully when starting with a clean
    system!

    $ opkg_root=/openpkg
    $ opkg_ugid=openpkg
    $ _

    The example code snippets in this reference use shell variables for added
    convenience, but feel free to substitute actual commands in their place.

  o Boostrapping OpenPKG from scratch:

    An OpenPKG instance lives in its own self-contained and self-controlled
    dedicated filesystem hierarchy ($opkg_root). To use OpenPKG on a machine
    without existing OpenPKG instance, bootstrap OpenPKG by downloading the
    latest openpkg-<V>-<R>.src.sh from ftp://ftp.openpkg.org/release/<V>/SRC/.
    When executed, this script establishes the OpenPKG hierarchy. This shell
    script can be executed by any user, but requires development tools like
    cc(1) and make(1).

    After the hierarchy is established, installation continues with a second
    script called openpkg-<V>-<R>.<arch>-<os>-<tag>.sh. Unlike the first
    script, this one dows not requires development tools. Installation
    requires root privileges to expand capabilities to the fullest extend.
    It will be installable and usable as a unprivileged user with limited
    functionality.

    $ ftp ftp.openpkg.org
    ftp> cd release/<M>.<N>/SRC
    ftp> ls openpkg-*.src.sh
    ftp> get openpkg-<V>-<R>.src.sh
    ftp> bye
    $ sh openpkg-<V>-<R>.src.sh --prefix=$opkg_root --user=$opkg_ugid --group=$opkg_ugid
    $ su -
    # sh openpkg-<V>-<R>.<arch>-<os>-<tag>.sh
    # exit
    $ _ 

  o Updating OpenPKG to the latest version:

    On a machine with an existing OpenPKG instance, or after bootstrapping
    OpenPKG from scratch (see the previous procedure), use OpenPKG to update
    OpenPKG! Download the latest openpkg-<V>-<R>.src.rpm from
    ftp://ftp.openpkg.org/release/<M>.<N>/, and follow the instructions to
    rebuild a binary package from source. Alternatively, get the latest
    openpkg-<V>-<R>.<arch>-<os>-<tag>.rpm, and follow the instructions to
    update or install a binary package.

  o Find a package in the package repository:

    To find a package and its version information you have to look
    for the package files at ftp://ftp.openpkg.org/release/<M>.<N>/.
    Alternative to this path, similar packages can be found at
    ftp://ftp.openpkg.org/current/. These packages may be less stable,
    however.

  o Prepare your shell environment:

    To more conveniently work with OpenPKG, modify the shell environment to
    meet the needs of the installed OpenPKG packages. Note that while such
    modifications may be convinient, the installed OpenPKG packages do not
    depend on them for successful operation. In fact, this step can be
    entirely skipped if only RPM operations are needed. In such a limited
    case, simply execute "$opkg_root/bin/openpkg rpm".

    To modify the shell environment, simply add the following command to your
    Bourne-Shell profile. Alternatively, the same command can be entered
    manually at the interactive shell prompt:

    $ eval `/cw/etc/rc --eval all env`
    $ _

  o To install OpenPKG packages:

    The most typical approach installing packages with OpenPKG involves doing
    'Fetch and build a binary package from source' and then 'Install or update a
    binary package' as described by the following sections. Do not ignore the
    second section regardless of how a binary package is obtained.

  o Fetch and build a binary package from source:

    Before any installation can occur, the files in a source package must be
    built into binaries (if such a binary package already exists, skip to the
    next bullet item.) The product of this building process is a binary
    package with a name like foo-<V>-<R>.<arch>-<os>-<tag>.rpm, The binary
    package is found in $opkg_root/RPM/PKG/. The following command will
    produce a binary package from source:

    $ openpkg rpm --rebuild ftp://ftp.openpkg.org/release/<M>.<N>/foo-<V>-<R>.src.rpm
    $ _

    Alternatively, to perform the steps behind the --rebuild option
    manually, enter the following commands:

    $ openpkg rpm -Uvh ftp://ftp.openpkg.org/release/<M>.<N>/foo-<V>-<R>.src.rpm
    $ cd $opkg_root/RPM/SRC/foo
    $ openpkg rpm -bb foo.spec
    $ _

    This procedure allows the spec file to be altered.

  o Install or update a binary package:

    $ su -
    # openpkg rpm -Uvh $opkg_root/RPM/PKG/foo-<V>-<R>.<arch>-<os>-<tag>.rpm
    # exit
    $ _

    Attention! When updating a package with a previously hand-modified
    configuration file, then OpenPKG first backs up this modified
    configuration file to filename.rpmsave. RPM announces this questionable
    act with a warning message.

    Unfortunately, this condition cannot be automatically resolved by RPM.
    Instead, each configuration file must be remodified by carefully comparing
    the package's default configuration with the earlier version's own
    modifications. Just moving back the file will result in the loss of any
    vendor configuration changes.

  o Downgrading a binary package:

    In case the latest version of a package does not work as expected, it is
    possible to revert to an older version. To downgrade a package to an older
    version, run the following command:

    $ su -
    # openpkg rpm -Uvh --oldpackage $opkg_root/RPM/PKG/foo-<V>-<R>.<arch>-<os>-<tag>.rpm
    # exit
    $ _

  o Configuring a package:

    Package configuration is package dependent. However, if a package uses a
    configuration file, it is always placed in $opkg_root/etc/foo/.  RPM tags
    such files as configuration files in order to treat them specially in
    later update operations, so feel free to edit these files. Adjustments to
    these configuration files will not be lost in subsequent package updates.

  o Running a package:

    A package can be manipulated by issuing "run commands" (rc) which are
    found in $opkg_root/etc/rc.d/rc.foo. These can be executed on system
    startup and shutdown time, on a regular interval (cron!), or manually by
    the OpenPKG user (you):

    $ su -
    # $opkg_root/etc/rc foo restart
    $ exit
    $ _

    Additionally, these RC scripts are controlled by various configuration
    variables. The variable names and their defaults can be listed by running
    the following command:

    $ $opkg_root/etc/rc --config
    $ _

    Environment variables can be set by writing shell script code in
    $opkg_root/etc/rc.conf which by default is created empty.

  o Query information about binary packages:

    - To list information about binary package:
      $ openpkg rpm -qpi $opkg_root/RPM/PKG/foo-<V>-<R>.<arch>-<os>-<tag>.rpm 

    - To list all files a binary package will install:
      $ openpkg rpm -qplv $opkg_root/RPM/PKG/foo-<V>-<R>.<arch>-<os>-<tag>.rpm 

  o Query information about installed packages:

    - To list all installed packages and their versions:
      $ openpkg rpm -qa                         

    - To list information about an installed package:
      $ openpkg rpm -qi foo

    - To list all files a package has installed:
      $ openpkg rpm -qlv foo

  o Verify the integrity of a package:

    RPM records summary information about each installed file and can
    use this information to verify the integrity of the package(s).

    - To check the integrity of all packages:
      $ openpkg rpm -Va

    - To check the integrity of a particular package:
      $ openpkg rpm -V foo

    - To check all package dependencies only:
      $ openpkg rpm -Va --nofiles

  o Deinstall (erase) a package:

    $ su -
    # openpkg rpm -e foo
    # exit
    $ _

  o Automating package building and installation with dependencies

    Use the "openpkg build" mechanism in openpkg-tools. To install the
    tools including their requirements of make, binutils and gcc, run

    $ su -
    # openpkg install openpkg-tools

    To create a shell script of commands to build and install a certain
    package including it's dependencies, run

    $ su -
    # openpkg build foo | sh

    Update all packages in dependency order

    $ su -
    # openpkg build -Ua | sh

    Explore the power of this tool by running "openpkg man build" 

@


1.25
log
@flush pending updates for OpenPKG 2.0
@
text
@d213 21
@


1.24
log
@update quick reference to reflect current reality
@
text
@d16 2
a17 2
    $ opkg_root=/cw
    $ opkg_ugid=cw
d20 1
a20 1
    The example code snippits in this reference use shell variables for added
d27 1
a27 1
    with no existing OpenPKG instance, bootstrap OpenPKG by downloading the
d34 5
a38 2
    script called openpkg-<V>-<R>.<arch>-<os>.<id>.sh. Unlike the first
    script, this one requires root privileges but no development tools.
d47 1
a47 1
    # sh openpkg-<V>-<R>.<arch>-<os>.<id>.sh
d58 1
a58 1
    openpkg-<V>-<R>.<arch>-<os>.<id>.rpm, and follow the instructions to
d76 1
a76 1
    case, simply execute $opkg_root/bin/rpm.
d87 2
a88 2
    The most typical approach to installing with OpenPKG involves doing 'Fetch
    and build a binary package from source' and then 'Install or update a
d97 1
a97 1
    package with a name like foo-<V>-<R>.<arch>-<os>.<id>.rpm, The binary
d101 1
a101 1
    $ rpm --rebuild ftp://ftp.openpkg.org/release/<M>.<N>/foo-<V>-<R>.src.rpm
d104 2
a105 2
    Alternatively, to perform the 'steps behind' option, --rebuild
    manually by entering the following commands:
d107 1
a107 1
    $ rpm -Uvh ftp://ftp.openpkg.org/release/<M>.<N>/foo-<V>-<R>.src.rpm
d109 1
a109 1
    $ rpm -bb foo.spec
d112 1
a112 2
    This 'steps behind' option is useful for adjusting the package
    specification.
d117 1
a117 1
    # rpm -Uvh $opkg_root/RPM/PKG/foo-<V>-<R>.<arch>-<os>.<id>.rpm
d139 1
a139 1
    # rpm -Uvh --oldpackage $opkg_root/RPM/PKG/foo-<V>-<R>.<arch>-<os>.<id>.rpm
d176 1
a176 1
      $ rpm -qpi $opkg_root/RPM/PKG/foo-<V>-<R>.<arch>-<os>.<id>.rpm 
d179 1
a179 1
      $ rpm -qplv $opkg_root/RPM/PKG/foo-<V>-<R>.<arch>-<os>.<id>.rpm 
d184 1
a184 1
      $ rpm -qa                         
d187 1
a187 1
      $ rpm -qi foo
d190 1
a190 1
      $ rpm -qlv foo
d198 1
a198 1
      $ rpm -Va
d201 1
a201 1
      $ rpm -V foo
d204 1
a204 1
      $ rpm -Va --nofiles
d209 1
a209 1
    # rpm -e foo
@


1.23
log
@remember rpm -Va --nofiles
@
text
@d38 1
a38 1
    ftp> cd release/<V>/SRC
d50 1
a50 1
    On a machine with an existing OpenPKG instance, or after boot- strapping
d52 2
a53 3
    OpenPKG! Download the latest openpkg-<V>-<R>.src.rpm with
    http://www.openpkg.org/pkg.cgi?package=openpkg or
    ftp://ftp.openpkg.org/release/<V>/, and follow the instructions to
d60 5
a64 5
    To find a package and its version information you can either browse the
    OpenPKG website at http://www.openpkg.org/pkg.cgi or look for the package
    files at ftp://ftp.openpkg.org/release/<V>. Alternative to this path,
    similar packages can be found at ftp://ftp.openpkg.org/current.
    These packages may be less stable, however.
d98 1
a98 1
    $ rpm --rebuild http://www.openpkg.org/pkg/foo-<V>-<R>.src.rpm
d104 1
a104 1
    $ rpm -Uvh http://www.openpkg.org/pkg/foo-<V>-<R>.src.rpm
@


1.22
log
@Backout change after Ralf's opinion that this is not needed, or maybe should
be 'binary' and not 'ascii'.
@
text
@d202 3
@


1.21
log
@Please review, I think we need to download using ASCII mode because the source
file is uuencoded and might otherwise be unencoded wrongly.

PR:
Submitted by:
Reviewed by:
Approved by:
Obtained from:
@
text
@a39 1
    ftp> ascii
@


1.20
log
@Beautification.
@
text
@d40 1
@


1.19
log
@Revised for release according to Peter's inspection.
@
text
@d11 4
a14 4
    All the following steps assume a permanent and unchanging filesystem
    path to OpenPKG and all its subsequently installed software packages.
    Choose the OpenPKG path and user/group ID carefully when starting with
    a clean system!
d20 2
a21 3
    The example code snippits in this reference use shell variables for
    added convenience, but feel free to substitute actual commands in
    their place.
d25 7
a31 7
    An OpenPKG instance lives in its own self-contained and self-
    controlled dedicated filesystem hierarchy ($opkg_root). To use
    OpenPKG on a machine with no existing OpenPKG instance, bootstrap
    OpenPKG by downloading the latest openpkg-<V>-<R>.src.sh from
    ftp://ftp.openpkg.org/release/1.0/SRC/. When executed, this script
    establishes the OpenPKG hierarchy. This shell script can be executed
    by any user, but requires development tools like cc(1) and make(1).
d33 2
a34 2
    After the hierarchy is established, installation continues with a
    second script called openpkg-<V>-<R>.<arch>-<os>.<id>.sh. Unlike the first
d38 1
a38 1
    ftp> cd release/1.0/SRC
d50 7
a56 7
    On a machine with an existing OpenPKG instance, or after boot-
    strapping OpenPKG from scratch (see the previous procedure), use
    OpenPKG to update OpenPKG! Download the latest openpkg-<V>-<R>.src.rpm
    with http://www.openpkg.org/pkg.cgi?package=openpkg or
    ftp://ftp.openpkg.org/release/1.0/, and follow the instructions to
    rebuild a binary package from source. Alternatively, get the
    latest openpkg-<V>-<R>.<arch>-<os>.<id>.rpm, and follow the instructions to
d61 5
a65 3
    To find a package and its version information you can either browse
    the OpenPKG website at http://www.openpkg.org/pkg.cgi or look for
    the package files at ftp://ftp.openpkg.org/release/.
d69 10
a78 10
    To more conveniently work with OpenPKG, modify the shell environment
    to meet the needs of the installed OpenPKG packages. Note that while
    such modifications may be convinient, the installed OpenPKG packages
    do not depend on them for successful operation. In fact, this step
    can be entirely skipped if only RPM operations are needed. In such
    a limited case, simply execute $opkg_root/bin/rpm.

    To modify the shell environment, simply add the following command
    to your Bourne-Shell profile. Alternatively, the same command can
    be entered manually at the interactive shell prompt:
d85 4
a88 4
    The most typical approach to installing with OpenPKG involves doing
    'Fetch and build a binary package from source' and then 'Install or
    update a binary package' as described by the following sections. Do not
    ignore the second section regardless of how a binary package is obtained.
d92 6
a97 6
    Before any installation can occur, the files in a source package
    must be built into binaries (if such a binary package already
    exists, skip to the next bullet item.) The product of this building
    process is a binary package with a name like foo-<V>-<R>.<arch>-<os>.<id>.rpm,
    The binary package is found in $opkg_root/RPM/PKG/. The following
    command will produce a binary package from source:
d122 2
a123 2
    configuration file to filename.rpmsave. RPM announces this
    questionable act with a warning message.
d125 5
a129 5
    Unfortunately, this condition cannot be automatically resolved by
    RPM. Instead, each configuration file must be remodified by carefully
    comparing the package's default configuration with the earlier
    version's own modifications. Just moving back the file will result
    in the loss of any vendor configuration changes.
d133 3
a135 3
    In case the latest version of a package does not work as expected,
    it is possible to revert to an older version. To downgrade a
    package to an older version, run the following command:
d144 5
a148 6
    Package configuration is package dependent. However, if a package
    uses a configuration file, it is always placed in $opkg_root/etc/foo/.
    RPM tags such files as configuration files in order to treat them
    specially in later update operations, so feel free to edit these
    files. Adjustments to these configuration files will not be lost in
    subsequent package updates.
d154 2
a155 2
    startup and shutdown time, on a regular interval (cron!), or manually
    by the OpenPKG user (you):
d162 3
a164 3
    Additionally, these RC scripts are controlled by various
    configuration variables. The variable names and their defaults can
    be listed by running the following command:
@


1.18
log
@Corrected wrong file path.
@
text
@d30 1
a30 1
    ftp://ftp.openpkg.org/current/SRC/. When executed, this script
d39 1
a39 1
    ftp> cd current/SRC
d55 1
a55 1
    ftp://ftp.openpkg.org/current/, and follow the instructions to
d64 1
a64 1
    the package files at ftp://ftp.openpkg.org/current/.
@


1.17
log
@Bugfixed and clarified section regarding installation of packages.
@
text
@d115 1
a115 1
    # rpm -Uvh $opkg_root/RPM/PGK/foo-<V>-<R>.<arch>-<os>.<id>.rpm
d137 1
a137 1
    # rpm -Uvh --oldpackage $opkg_root/RPM/PGK/foo-<V>-<R>.<arch>-<os>.<id>.rpm
@


1.16
log
@update path
@
text
@d66 1
a66 1
  o Prepare your shell environment
d82 8
a89 1
  o Fetch and rebuild a binary package from source (optional):
d112 1
a112 1
  o Install/update a binary package:
@


1.15
log
@Big beauty change - removed one newline character.
@
text
@d30 3
a32 3
    ftp://ftp.openpkg.org/current/. When executed, this script establishes
    the OpenPKG hierarchy. This shell script can be executed by any user,
    but requires development tools like cc(1) and make(1).
d39 1
a39 1
    ftp> cd current
@


1.14
log
@Passive voice/pronoun usage style correction.
@
text
@d23 1
a23 1
  
d33 1
a33 1
    
a81 1

d96 1
a96 1
  
@


1.13
log
@add info about downgrading a package
@
text
@d127 2
a128 2
    you can easily downgrade to an older version by running the
    following command:
@


1.12
log
@include feedback from hosting team
@
text
@d124 11
@


1.11
log
@Added clarification, and removed almost all instances of the word 'you' and 'your'.
@
text
@d1 1
d5 4
d29 1
a29 1
    OpenPKG by downloading the latest openpkg-V-R.src.sh from
d35 1
a35 1
    second script called openpkg-V-R.arch-os-id.sh. Unlike the first
d41 1
a41 1
    ftp> get openpkg-V-R.src.sh
d43 1
a43 1
    $ sh openpkg-V-R.src.sh --prefix=$opkg_root --user=$opkg_ugid --group=$opkg_ugid
d45 1
a45 1
    # sh openpkg-V-R.arch-os-id.sh
d53 1
a53 1
    OpenPKG to update OpenPKG! Download the latest openpkg-V-R.src.rpm
d57 1
a57 1
    latest openpkg-V-R.arch-os-id.rpm, and follow the instructions to
d88 1
a88 1
    process is a binary package with a name like foo-V-R.arch-os-id.rpm,
d92 1
a92 1
    $ rpm --rebuild http://www.openpkg.org/pkg/foo-V-R.src.rpm
d98 1
a98 1
    $ rpm -Uvh http://www.openpkg.org/pkg/foo-V-R.src.rpm
d109 1
a109 1
    # rpm -Uvh $opkg_root/RPM/PGK/foo-V-R.arch-os-id.rpm
d158 1
a158 1
      $ rpm -qpi $opkg_root/RPM/PKG/foo-V-R.arch-os-id.rpm 
d161 1
a161 1
      $ rpm -qplv $opkg_root/RPM/PKG/foo-V-R.arch-os-id.rpm 
d191 1
@


1.10
log
@'env:sh' was renamed to just 'env'
@
text
@d4 6
a9 1
  o Global decision on OpenPKG filesystem root path and user/group id:
a10 5
    All following steps assume a once decided and then fixed filesystem
    path and Unix user/group id. For convinience reasons we use shell
    variables, but feel free to directly substitute them in your
    particular commands.
  
d15 4
d21 11
a31 8
    An OpenPKG instance lives in its own self-contained and
    self-controlled dedicated filesystem hierarchy ($opkg_root) which
    has to be bootstrapped from scratch. For this you have to fetch
    the latest openpkg-V-R.src.sh from ftp://ftp.openpkg.org/current/,
    build it and let it establish the hierarchy. The build step can
    be performed as any user, and requires development tools installed
    (mainly cc(1) and make(1)). The installation step requires root
    priviledges but does not require development tools.
d46 8
a53 7
    If you did the bootstrapping procedure before, you can already use
    OpenPKG to update OpenPKG! Determine the latest openpkg-V-R.src.rpm
    from http://www.openpkg.org/pkg.cgi?package=openpkg or
    ftp://ftp.openpkg.org/current/ and follow the instructions
    to rebuild a binary package from source or get the latest
    openpkg-V-R.arch-os-id.rpm, and follow the instructions to
    update/install a binary package.
d57 3
a59 4
    In order to find a package and/or its version information
    you can either browse the OpenPKG website under
    http://www.openpkg.org/pkg.cgi or look for the package files under
    ftp://ftp.openpkg.org/current/.
d63 10
a72 10
    In order to conviniently work with OpenPKG, you can modify your
    shell environment to include all the environment changes requested
    by the currently installed OpenPKG packages. Note that this modifi-
    cation is only a matter of convinience, though. OpenPKG packages
    do not depend on it for successful operation. In fact, if your
    intentions are limited to RPM operations you can skip this step
    entirely and just execute $opkg_root/bin/rpm.

    If you decide to modify your shell environment after all, simply
    add the following command to your Bourne-Shell profile:
a76 2
    The same command can be entered manually at the interactive shell
    prompt.
d81 5
a85 6
    must be built into binaries (if you already have a binary package
    skip to the next bullet item.) The product of this building process
    is a binary package with a name like foo-V-R.arch-os-id.rpm. The
    binary package is found in $opkg_root/RPM/PKG/.

    The following command will produce a binary package from source:
d90 2
a91 3
    Alternatively, by entering the following commands one can perform
    the 'steps behind' option --rebuild manually. This option appeals
    to those wanting to adjust the package specification.
d98 3
d108 4
a111 4
    Attention! If you update a package with a configuration file that
    you had modified in the package's previous version, then your
    modified file will be backed up to filename.rpmsave. RPM will
    announce this questionable act with a warning message.
d114 4
a117 4
    RPM. You must redo your modifications for each file by carefully
    comparing the package's default configuration with your own
    modifications. Just moving back the file will result in loss of
    vendor changes.
d123 3
a125 3
    Feel free to edit these files. RPM tags them as configuration files
    in order to treat them specially on later update operations. This
    ensures that adjustments to configuration files are not lost in
d130 2
a131 2
    A package can be controlled by some "run commands" (rc) which are
    placed in $opkg_root/etc/rc.d/rc.foo. These are executed on system
d133 1
a133 1
    by you:
@


1.9
log
@Grammar, usage, and style corrections. Also added or removed minor content to
clarify some topics.
@
text
@d67 1
a67 1
    $ eval `/cw/etc/rc --eval all env:sh`
@


1.8
log
@enhance quick reference by adding lots of more details
@
text
@a0 1

d22 1
a22 1
    be performed as any user and requires development tools installed
d44 1
a44 1
    openpkg-V-R.arch-os-id.rpm and follow the instructions to
d57 9
a65 8
    shell environment by including all environment changes requested
    by the already installed OpenPKG packages. This is just for
    convinience, OpenPKG packages theirself do not depend on this
    for successful operation, of course. That is, for the purpose
    of just running RPM you could skip this step and just execute
    $opkg_root/bin/rpm instead, too. For convinience reasons add the
    following command to your Bourne-Shell profile or execute it
    manually at the interactive shell prompt:
d70 3
d75 7
a81 4
    One can only install binary packages. For this they can be
    built from source packages with the following command. The
    result is a binary package foo-V-R.arch-os-id.rpm placed under
    $opkg_root/RPM/PKG/.
d86 3
a88 3
    Alternatively one can perform the steps behind option --rebuild
    manually (which is interesting in case one wants to adjust the
    package specification):
d102 10
a111 9
    If you update a package that contains a configuration file and you
    made modifications to that file and the updated configuration comes
    with a default different from the previous configuration then your
    modified file is saved to filename.rpmsave and RPM outputs a warning
    message. This condition cannot be automatically resolved. You must
    redo your modifications for each file by examining carefully what
    has changed in the default configurations versus your modifications
    to the initial default. Just moving back the file will result in
    loss of vendor changes.
d115 6
a120 6
    Package configuration is package dependent. However, configuration
    (if used by a package) is always placed into $opkg_root/etc/foo/.
    Feel free to edit those files - they are tagged as configuration
    files and RPM treats them specially on update operations in order to
    make sure your adjustments are not lost. 
    
d126 1
a126 1
    startup and shutdown time, on a regular interval (cron!) or manually
d134 1
a134 1
    Additionally those RC scripts are controlled by various
d141 3
a143 5
    Each variable can be overridden from the shell script
    $opkg_root/etc/rc.conf which by default is empty but can contain
    arbitrary shell code written by you in order to adjust those
    variables.
    
d146 1
a146 1
    - List information about binary package:
d149 1
a149 1
    - List all files a binary package will install:
d154 1
a154 1
    - List all installed packages and their versions:
d157 1
a157 1
    - List information about an installed package:
d160 1
a160 1
    - List all files a package has installed:
d168 1
a168 1
    - Check the integrity of all packages:
d171 1
a171 1
    - Check the integrity of a particular packages:
a179 1

@


1.7
log
@general purpose shell environment
@
text
@d5 1
a5 1
  o getting OpenPKG up and running from scratch (bootstrapping)
d7 81
a87 6
    Get the latest openpkg-x.x-x.src.sh from http://www.openpkg.org/pkg.cgi?package=openpkg
    # sh openpkg-x.x-x.src.sh --prefix=/cw --user=cw --group=cw
    # sh openpkg-x.x-x.arch-os-id.sh
    The first step requires development tools on the machine. The second step
    does not require those tools but doesn't allow you to choose the prefix,
    user or group.
d89 1
a89 1
  o updating OpenPKG to the latest version
d91 4
a94 6
    If you did the bootstrapping procedure before, use OpenPKG to update
    OpenPKG!  Get the latest openpkg-x.x-x.src.rpm from
    http://www.openpkg.org/pkg.cgi?package=openpkg and follow the
    instructions to rebuild a binary package from source or get the latest
    openpkg-x.x-x.arch-os-id.rpm and follow the instructions to update/
    install a binary package.
d96 9
a104 1
  o find a package in the package repository on the web
d106 1
a106 1
    http://www.openpkg.org/pkg.cgi
d108 6
a113 1
  o prepare your shell environment
d115 28
a142 4
    $ eval `/cw/etc/rc --eval all env:sh`
    This modifies your shell environment for OpenPKG including all environment
    changes neccesary for already installed packages. For the wholly purpose
    of running rpm you can skip this step and execute /cw/bin/rpm instead.
d144 2
a145 1
  o get and rebuild a binary package from source (optional)
d147 1
a147 4
    This is the foolproof method
    $ rpm --rebuild http://www.openpkg.org/pkg/myfavourite-x.x.x-x.src.rpm
  
  o get and install/ build a binary package from source (optional)
d149 2
a150 3
    This gives you more manual control about what's going on.
    $ rpm -Uvh http://www.openpkg.org/pkg/myfavourite-x.x.x-x.src.rpm
    $ rpm -bb /cw/RPM/SRC/myfavourite/myfavourite.spec
d152 2
a153 1
  o get and update/ install a binary package
d155 2
a156 9
    # rpm -Uvh /cw/RPM/PGK/myfavourite-x.x.x-x.arch-os-id.rpm
    If you update a package that contains a configuration file and you made
    modificatins to that file and the updated configuration comes with a
    default different from the previous configuration then your modified file
    is saved to filename.rpmsave. This condition cannot be automatically
    resolved. You must redo your modifications for each file by examining
    carefully what has changed in the default configurations versus your
    modifications to the initial default. Just moving back the file will
    result in loss of vendor changes.
d158 1
a158 1
  o configure a package
d160 2
a161 4
    Package configuration is package dependent. However, configuration is
    *always* placed into /cw/etc/myfavourite/, variable data are always placed
    into /cw/var/myfavourite/ ... daemons are always (re)started and stopped
    using /cw/etc/rc myfavourite (stop|start).
d163 2
a164 1
  o query all installed packages
d166 2
a167 1
    $ rpm -qa
d169 1
a169 1
  o erase a package
d171 4
a174 1
    $ rpm -e myfavourite
@


1.6
log
@test
@
text
@d29 4
a32 2
    $ . /cw/etc/rc.env
    This prefixes your (MAN|INFO|LD_LIBRARY)PATH with those from OpenPKG.
a70 1

@


1.5
log
@test
@
text
@d70 1
@


1.4
log
@test
@
text
@a69 1

@


1.3
log
@more details about .rpmsave issues
@
text
@d70 1
@


1.2
log
@sneak preview
@
text
@d46 8
a53 3
    If you update a package that contains a configuration file *and* you
    changed the default config previously then OpenPKG saves your changes in
    filename.rpmsave. You must redo your previous changes for each file.
@


1.1
log
@add template
@
text
@d5 59
a63 1
  o ...
@