OpenPKG CVS Repository
http://cvs.openpkg.org/
____________________________________________________________________________
Server: cvs.openpkg.org Name: Thomas Lotterer
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-doc Date: 25-Feb-2004 10:23:57
Branch: HEAD Handle: 2004022509235700
Modified files:
openpkg-doc/quickref openpkg.txt
Log:
flush pending updates for OpenPKG 2.0
Summary:
Revision Changes Path
1.25 +32 -30 openpkg-doc/quickref/openpkg.txt
____________________________________________________________________________
patch -p0 <<'@@ .'
Index: openpkg-doc/quickref/openpkg.txt
============================================================================
$ cvs diff -u -r1.24 -r1.25 openpkg.txt
--- openpkg-doc/quickref/openpkg.txt 21 Mar 2002 20:50:44 -0000 1.24
+++ openpkg-doc/quickref/openpkg.txt 25 Feb 2004 09:23:57 -0000 1.25
@@ -13,26 +13,29 @@
the OpenPKG path and user/group ID carefully when starting with a clean
system!
- $ opkg_root=/cw
- $ opkg_ugid=cw
+ $ opkg_root=/openpkg
+ $ opkg_ugid=openpkg
$ _
- The example code snippits in this reference use shell variables for added
+ 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
- with no existing OpenPKG instance, bootstrap OpenPKG by downloading the
+ 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>.<id>.sh. Unlike the first
- script, this one requires root privileges but no development tools.
+ 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
@@ -41,7 +44,7 @@
ftp> bye
$ sh openpkg-<V>-<R>.src.sh --prefix=$opkg_root --user=$opkg_ugid
--group=$opkg_ugid
$ su -
- # sh openpkg-<V>-<R>.<arch>-<os>.<id>.sh
+ # sh openpkg-<V>-<R>.<arch>-<os>-<tag>.sh
# exit
$ _
@@ -52,7 +55,7 @@
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>.<id>.rpm, and follow the instructions to
+ 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:
@@ -70,7 +73,7 @@
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.
+ 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
@@ -81,8 +84,8 @@
o To install OpenPKG packages:
- The most typical approach to installing with OpenPKG involves doing 'Fetch
- and build a binary package from source' and then 'Install or update a
+ 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.
@@ -91,28 +94,27 @@
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 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:
- $ rpm --rebuild ftp://ftp.openpkg.org/release/<M>.<N>/foo-<V>-<R>.src.rpm
+ $ openpkg rpm --rebuild
ftp://ftp.openpkg.org/release/<M>.<N>/foo-<V>-<R>.src.rpm
$ _
- Alternatively, to perform the 'steps behind' option, --rebuild
- manually by entering the following commands:
+ Alternatively, to perform the steps behind the --rebuild option
+ manually, enter the following commands:
- $ rpm -Uvh ftp://ftp.openpkg.org/release/<M>.<N>/foo-<V>-<R>.src.rpm
+ $ openpkg rpm -Uvh ftp://ftp.openpkg.org/release/<M>.<N>/foo-<V>-<R>.src.rpm
$ cd $opkg_root/RPM/SRC/foo
- $ rpm -bb foo.spec
+ $ openpkg rpm -bb foo.spec
$ _
- This 'steps behind' option is useful for adjusting the package
- specification.
+ This procedure allows the spec file to be altered.
o Install or update a binary package:
$ su -
- # rpm -Uvh $opkg_root/RPM/PKG/foo-<V>-<R>.<arch>-<os>.<id>.rpm
+ # openpkg rpm -Uvh $opkg_root/RPM/PKG/foo-<V>-<R>.<arch>-<os>-<tag>.rpm
# exit
$ _
@@ -134,7 +136,7 @@
version, run the following command:
$ su -
- # rpm -Uvh --oldpackage $opkg_root/RPM/PKG/foo-<V>-<R>.<arch>-<os>.<id>.rpm
+ # openpkg rpm -Uvh --oldpackage
$opkg_root/RPM/PKG/foo-<V>-<R>.<arch>-<os>-<tag>.rpm
# exit
$ _
@@ -171,21 +173,21 @@
o Query information about binary packages:
- To list information about binary package:
- $ rpm -qpi $opkg_root/RPM/PKG/foo-<V>-<R>.<arch>-<os>.<id>.rpm
+ $ openpkg rpm -qpi $opkg_root/RPM/PKG/foo-<V>-<R>.<arch>-<os>-<tag>.rpm
- To list all files a binary package will install:
- $ rpm -qplv $opkg_root/RPM/PKG/foo-<V>-<R>.<arch>-<os>.<id>.rpm
+ $ 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:
- $ rpm -qa
+ $ openpkg rpm -qa
- To list information about an installed package:
- $ rpm -qi foo
+ $ openpkg rpm -qi foo
- To list all files a package has installed:
- $ rpm -qlv foo
+ $ openpkg rpm -qlv foo
o Verify the integrity of a package:
@@ -193,18 +195,18 @@
use this information to verify the integrity of the package(s).
- To check the integrity of all packages:
- $ rpm -Va
+ $ openpkg rpm -Va
- To check the integrity of a particular package:
- $ rpm -V foo
+ $ openpkg rpm -V foo
- To check all package dependencies only:
- $ rpm -Va --nofiles
+ $ openpkg rpm -Va --nofiles
o Deinstall (erase) a package:
$ su -
- # rpm -e foo
+ # openpkg rpm -e foo
# exit
$ _
@@ .
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
