@
1.22
log
@updated grid.png
@
text
@d3 1
a3 1
Prerequisites
OpenPKG by design makes minimal assumptions about the underlying operating system, but some basic things need to be checked.Platform
The less you know about OpenPKG the more important is that you are using a supported primary or at least secondary [*] platform. The following table uses a row for each supported platform and gives three names for it in different columns. You will find that OpenPKG software uses arch-os to create filenames and the same ones are used on the ftp download site. Humans and documentation use what is shown below platform. To ensure that we really talk about the same thing, enter the uname command in a shell and find the output of the rightmost column. d88 20 a107 12Permission
Additionally make sure you have root access to your system. Although it is not necessary to work out the whole stuff as root, we do need this in the later stages of our example installation. Keep in mind that OpenPKG can be used in a limited way without having root access but this is not discussed here. d123 9 a131 9 Also make sure you have approximately 250MB free disk space on the filesystem were OpenPKG should be loaded. The installation procedure creates a directory for the OpenPKG instance but it also accepts a pre-existing directory or a symlink to a pre-existing directory and will use it. The downloadable binary packages use the prefix /cw and so does this tutorial. However, using source packages it is possible to use an arbitrary prefix and in fact the OpenPKG architecture allows any number of parallel and simultaneous instances on a single system - until a critical resource is exhausted. d135 1 a135 1 $ ln -s /storage/with/250MB/free /cw d140 3 a142 3 For our example you should have approximately 250MB of temporary disk space available somewhere. OpenPKG reads the environment variable TMPDIR to locate an hopefully large workspace. d145 1 a145 1 $ TMPDIR= /tmp/with/250MB/free d151 8 a158 11 require development tools like make and [g]cc as well. There is no ultimate standard that tells what a minimal toolset is, so we have to traverse some fog here. For regular installations with an existing OpenPKG bootstrap, indicated by an executable prefix/bin/rpm, there are nearly zero additional system requirements. However, the bootstrap process needs a little help and requires sh, tar, ftp and uudecode (Attention: United Linux seems to have moved this into a optional sharutils system package) in the PATH. Also if you want to install a compiler package from source, you need a vendor compiler first. To tell OpenPKG about your favorite Source or Binary While we strongly recommend you to use source packages whenever possible, the absence of development tools is the number one reason which enforces the use of binaries for deployment. Let's make a quick'n'dirty but mostly useful check:$ which gcc cc || echo "bad luck, no development tools"The matrix below tells you about all four combinations of bootstrapping or regular installing/upgrading a package from source or binary. For the tutorial, please select the bootstrap method you prefer or require. Then come back and continue below.
Release Engineering
Those who have installed unreleased packages from CURRENT, STABLE or SNAPSHOTs should be aware of the principles behind OpenPKG release engineering. Note that the version numbers of these packages are formatted as timestamps rather than what is expected from a released package. Decoding such version numbers yields very large integers. Any RELEASE package will clearly have a lower number even if it is a more mature version of the same package!For this reason, switching from a unpublished package to a official released package is considered a 'downgrade' by RPM. This works by design according to the OpenPKG standards of release engineering. To easily upgrade or downgrade such uncooperative packages in general, RPM offers the options --oldpackage and --nodeps to be added to d178 1 a178 1
Matrix
d188 14 a201 2 Select one of the four installation examples in the matrix above to begin the tutorial and make a regular installation of bash-Fine tuning
Do you want your shell to use the new OpenPKG environment so that you have the /cw/bin in your PATH, can read the man pages using the correct MANPATH etc.? There's a single command that does all of this for you. Place it in your favourite shell's profile.$ eval `/cw/etc/rc --eval all env` d210 1 a210 1 $ set | grep /cw/ d215 12 a226 1Want more packages?
d232 1 a232 1Bootstrap from source
d234 6 a239 5 A warning is due for all who decide to bootstrap OpenPKG with existing OpenPKG installations, because bootstrapping into an existing OpenPKG hierarchy (such as /cw) discards the contents of its internal RPM database! When learning OpenPKG, it is safest to bootstrap into an empty directory which OpenPKG will automatically create for you if not existing. d241 4 a244 4 Should an upgrade of the actual OpenPKG itself be desired, this is not carried out by bootstrapping again. Rather, install the next OpenPKG version just as any other package. Go back to the matrix to see the upgrade options again. d261 7 a267 1 $ sh openpkg-.0- d270 1 a270 1 \# sh openpkg-.0.src.sh --prefix=/cw --user=cw --group=cw .0- d276 2 d279 1 a279 1.0.arch-os-cw.sh Bootstrap from binary
d281 6 a286 5 A warning is due for all who decide to boostrap OpenPKG with existing OpenPKG installations, because bootstrapping into an existing OpenPKG hierarchy (such as /cw) discards the contents of its internal RPM database! When learning OpenPKG, it is safest to bootstrap into an empty directory which OpenPKG will automatically create for you if not existing. d288 4 a291 4 Should an upgrade of the actual OpenPKG itself be desired, this is not carried out by bootstrapping again. Rather, install the next OpenPKG version just as any other package. Go back to the matrix to see the upgrade options again. d305 1 a305 1 ftp> get arch-os/openpkg-.0- d310 1 a310 1 \# sh openpkg-.0.arch-os-cw.sh .0- d316 2 d319 1 a319 1.0.arch-os-cw.sh Regular installation/update from source
d322 1 a322 1 $ /cw/bin/rpm --rebuild \\ d325 2 a326 2 \# /cw/bin/rpm -Uvh \\ /cw/RPM/PKG/foo-X.Y-.0.arch-os-cw.rpm d334 17 a350 7 /cw/RPM/PKG/bash-- /cw/RPM/PKG/bash-.0.ix86-freebsd4.8-cw.rpm - /cw/RPM/PKG/bash-.0.ix86-freebsd5.1-cw.rpm - /cw/RPM/PKG/bash-.0.ix86-linux2.2-cw.rpm - /cw/RPM/PKG/bash-.0.ix86-linux2.4-cw.rpm - /cw/RPM/PKG/bash-.0.sparc64-solaris2.8-cw.rpm - /cw/RPM/PKG/bash-.0.sparc64-solaris2.9-cw.rpm - d354 2 d357 1 a357 1.0.ix86-solaris2.9-cw.rpm Regular installation/update from binary
d361 2 a362 2 \# /cw/bin/rpm -Uvh \\ ftp://ftp.openpkg.org/release//BIN/platform/foo-X.Y- d366 17 a382 9 ftp://ftp.openpkg.org/release/.0.arch-os-cw.rpm /BIN/ix86-freebsd4.8/bash- ftp://ftp.openpkg.org/release/- .0.ix86-freebsd4.8-cw.rpm /BIN/ix86-freebsd5.1/bash- ftp://ftp.openpkg.org/release/- .0.ix86-freebsd5.1-cw.rpm /BIN/ix86-debian2.2/bash- ftp://ftp.openpkg.org/release/- .0.ix86-linux2.2-cw.rpm /BIN/ix86-debian3.0/bash- ftp://ftp.openpkg.org/release/- .0.ix86-linux2.4-cw.rpm /BIN/ix86-redhat9/bash- ftp://ftp.openpkg.org/release/- .0.ix86-linux2.4-cw.rpm /BIN/ix86-suse8.2/bash- ftp://ftp.openpkg.org/release/- .0.ix86-linux2.4-cw.rpm /BIN/sparc64-solaris8/bash- ftp://ftp.openpkg.org/release/- .0.sparc64-solaris2.8-cw.rpm /BIN/sparc64-solaris9/bash- ftp://ftp.openpkg.org/release/- .0.sparc64-solaris2.9-cw.rpm /BIN/ix86-solaris9/bash- @ 1.21 log @spell checking and correcting @ text @d141 4 a144 4 @ 1.20 log @more infos about both tables; improve download URL @ text @d71 1 a71 1 use an arbitrary prefix and in fact the OpenPKG architecture allowes any d103 1 a103 1 first. To tell OpenPKG about your favourite get platform/openpkg-- .0.ix86-solaris2.9-cw.rpm .0- @ 1.18 log @flush everything prepared for OpenPKG 1.2 @ text @d3 1 a3 1.0.arch-os-cw.sh 1.1 d10 4 a13 4 This tutorial guides you on your way into the world of OpenPKG showing you how to bootstrap OpenPKG and install GNU Bash as an example. For more details about the commands used, see the OpenPKG Quick Reference or refer to the d19 2 d22 4 a25 2 Ensure that your system is one of the fully supported platforms: d30 6 a35 2ix86-freebsd4.7 FreeBSD 4.7 FreeBSD 4.7-STABLE i386 d38 3 a40 2 ix86-freebsd5.0 FreeBSD 5.0 FreeBSD 5.0-RELEASE i386 ix86-linux2.2 Debian GNU/Linux 2.2 Linux 2.2.22 i686 a41 1 a42 1 d47 1 a47 1 platform such as BSD, Linux, Solaris, Tru64, or HP-UX. For more details of d52 21 a72 6 ix86-linux2.4 Debian GNU/Linux 3.0 Linux 2.4.19 i686 Additionally make sure you have root access to your system. Although not always necessary, we do need this in the later stages of our example installation. Also make sure you have approximately 300MB free disk space on the / filesystem. You can move and symlink to some better places afterwards. d74 5 a78 1
Source or Binary?
d80 6 d87 2 a88 2 absence of development tools is the number one reason to be forced to use binaries. Let's make a quick'n'dirty but mostly useful check: d91 1 a91 1 $ which gcc cc || echo "you don't have a compiler, so must use binaries" d94 1 a94 1 The following matrix tells you about all combinations of bootstrapping or d99 2 a100 2Those who have installed unreleased packages from CURRENT or SNAPSHOTs should a106 1 d109 1 a109 1 one is considered a 'downgrade' by RPM. This works by design according to the d111 3 a113 3 upgrade or downgrade such uncooperative packages in general, RPM makes available the options --oldpackage and --nodeps. It is neccessary to use only one of these RPM command line options, or sometimes both. d115 1 a115 1
d124 1 a124 2
Example Installation
d132 1 a132 2Environment
d151 1 a151 2 see the Package Repository. d169 1 a169 1 $ cd /tmp d186 1 a186 1 \# cd /tmp d207 1 a207 1 $ cd /tmp d223 1 a223 1 \# cd /tmp d246 2 a247 1 /cw/RPM/PKG/bash-- d252 1 d266 9 a274 6 ftp://ftp.openpkg.org/release/.0.ix86-freebsd4.6-cw.rpm /BIN/freebsd-4.6/bash- ftp://ftp.openpkg.org/release/- .0.ix86-freebsd4.6-cw.rpm /BIN/debian-2.2/bash- ftp://ftp.openpkg.org/release/- .0.ix86-linux2.2-cw.rpm /BIN/debian-3.0/bash- ftp://ftp.openpkg.org/release/- .0.ix86-linux2.4-cw.rpm /BIN/redhat-7.2/bash- ftp://ftp.openpkg.org/release/- .0.ix86-linux2.4-cw.rpm /BIN/solaris-8/bash- ftp://ftp.openpkg.org/release/- .0.sparc64-solaris2.8-cw.rpm /BIN/solaris-9/bash- @ 1.17 log @Updated to reflect current platform requirements that are fully supported. @ text @d22 3 a24 1- .0.sparc64-solaris2.9-cw.rpm
Example PKG pathes
@ 1.13 log @Corrections, clarifications, and rewording. @ text @d3 2 a4 1Bootstrapping/Upgrading
First, we need to fetch some material.$ cd /tmp $ ftp ftp.openpkg.org Connected to ftp.openpkg.org. 220 ftp.openpkg.org OpenPKG Anonymous FTP Server ready. Name (ftp.openpkg.org): anonymous 331 Anonymous login ok, send your complete email address as your password. Password: you@@example.com 230- [...] Welcome to OpenPKG.org! [...] 230 Anonymous access granted, restrictions apply. ftp> bin 200 Type set to I.
Do you need binaries and have a vanilla machine without any previous instance of OpenPKG? Then do this:
ftp> cd release/1.0/BIN ftp> get openpkg-1.0.0-1.0.0.arch-os-cw.sh ftp> get bash-2.05a-1.0.0-arch-os-cw.rpm
Do you need binaries, already bootstrapped your machine and want to upgrade OpenPKG? Then do this:
ftp> cd release/1.0/BIN ftp> get openpkg-1.0.0-1.0.0-arch-os-cw.rpm ftp> get bash-2.05a-1.0.0-arch-os-cw.rpm
Do you want source and have a vanilla machine without any previous instance of OpenPKG? Do this:
ftp> cd release/1.0/SRC ftp> get openpkg-1.0.0-1.0.0.src.sh ftp> get bash-2.05a-1.0.0.src.rpm
Do you want source, already bootstrapped your machine and want to upgrade OpenPKG? Do this:
ftp> cd release/1.0/SRC ftp> get openpkg-1.0.0-1.0.0.src.rpm ftp> get bash-2.05a-1.0.0.src.rpm
ftp> bye 221 Goodbye.If you preferred source we have to prepare the arch-os-cw bootstrap script and build the bootstrap RPM package. This guide assumes that you create your new cool world below /cw using the to-be-created user "cw" and group "cw" and thus stick with that default. OpenPKG does not force you to do that.
$ sh openpkg-1.0.0-1.0.0.src.sh --prefix=/cw --user=cw --group=cwRemember the binary download options above? We now have essentially the same files available. Upgraders do not have the arch-os-cw bootstrap script. They don't need it anyway as the already bootstrapped.
$ ls openpkg* openpkg-1.0.0-1.0.0.arch-os-cw.rpm openpkg-1.0.0-1.0.0.arch-os-cw.sh openpkg-1.0.0-1.0.0.src.rpmIf you're upgrading from source you have to build the binary now.
$ /cw/bin/rpm --rebuild openpkg-1.0.0-1.0.0.src.rpmNow the remaining tasks do real installation work and require root privileges.
$ su \#Unless you're upgrading execute the bootstrap script now.
\# sh openpkg-1.0.0-1.0.0.arch-os-cw.shNow to upgrade you just have to install OpenPKG as a OpenPKG package. This was already part of the previous bootstrap script so if you did it you don't have to do the OpenPKG upgrade installation. Otherwise execute the upgrade command.
\# /cw/bin/rpm -Uvh openpkg-1.0.0-1.0.0.arch-os-cw.rpmrelease root priviledges. d62 1 a62 1 and --nodeps and add (one of) them to the command line listed above. d64 8 a71 9
\# exit $READY! No matter if you build from source or binary, had a vanilla system or did an upgrade, the downloaded version of OpenPKG is installed, up and running. Think how short this instructions would have been if we'd coverd just one of all those cases. d75 2 a76 2 So now head for the bash installation. We already downloaded the bash RPM package before. a77 15 If you preferred source ...
$ /cw/bin/rpm --rebuild bash-2.05a-1.0.0.src.rpmNow you have the binary, either just built or download previously. Install it. If you build the binary it is located in /cw/RPM/PKG. Use the correct path in the command listed below.
$ su \# /cw/bin/rpm -Uvh /cw/RPM/PKG/bash-2.05a-arch-os-cw.rpm \# exitDONE! d103 74 a176 1 see Package Repository @ 1.8 log @cleanups @ text @d46 1 a46 1 $ which gcc cc || echo "you don't have a compiler, so must use binaries" d71 1 a71 4
Do you need binaries and have a vanilla machine without any previous instance of OpenPKG? Then do this: d75 1 d78 1 a78 4
Do you need binaries, already bootstrapped your machine and want to upgrade OpenPKG? Then do this: d84 2 a85 1 Do you want source and have a vanilla machine without any previous instance of OpenPKG? Do this: d91 2 a92 1 Do you want source, already bootstrapped your machine and want to upgrade OpenPKG? Do this: d95 1 a95 1 ftp> get openpkg-1.0.0-1.0.0.rpm d98 2 d112 1 a112 1 Remember the binary download options above? We're now have essentially the d147 10 d191 19 d211 1 @ 1.7 log @fixed URLs @ text @d6 9 a14 7 This tutorial guides you on your way into the cool world of OpenPKG showing you how to bootstrap OpenPKG and install bash as an example package. For more details about the commands being used here see the Quick Reference or refer to the OpenPKG Handbook to dive deeper or take off and have a look at the Slideset for a birds' eye view. d18 1 a18 1 Ensure your system is running one of the supported platforms: d24 1 a24 2
User Tutorial
In the following, we will go into detail on how to use the RPM-based software packaging system OpenPKG from a users point of view. For this, we provide the essential steps and commands in a tutorial-style way. For more in-depth information about RPM you should read the book Maximum RPM, which we also provide online for your convinience.Platform Prerequisites
First, make sure that the underlying Unix platform is either Solaris, FreeBSD or Linux (run uname -a to determine this, if you don't know already). The particular currently supported platform versions are:- Solaris 2.[678]
- FreeBSD 4.[123]
- Debian GNU/Linux 2.2 ("Potato")
Filesystem Assumptions
The whole OpenPKG software package system is located on the Unix filesystem under a single root directory. At Cable & Wireless Deutschland this root directory is intuitively and uniquely named /cw. That is, why this tutorial uses this particular path from now on. But the whole package system is designed to work with an arbitrary root directory, although after performing the bootstrap procedure it is a fixed one.So, on non-C&W machines one would usually use perhaps /sw (for "software") instead, of course. It is just important that the path does not conflict with an area where the operating system vendor already placed files (like /opt under Solaris, /usr/local under FreeBSD, etc). Additionally the software packages are designed to also work for underpriviledged situations where no root (uid 0) access exists. Then the root directory is usually a sub-directory of a regular user's home directory, like /home/foo/sw.
Filesystem Layout
The /cw filesystem hierarchy directly resembles the commonly known /usr hierarchy, that is, it contains sub-directories which correspond to those one usually can find also under /usr: bin, etc, include, info, lib, libexec, man, sbin, share and var. All data in those sub-directories are managed by RPM.Additionally, there is a /cw/local area in analogon to /usr/local, which obviously contains machine-local stuff, i.e., software packages which are only interesting for the local machine and which were installed manually. So, this area is intentionally not managed by RPM. Nevertheless it also slightly resembles the layout of /usr, that is /cw/local contains the sub-directories bin, etc, include, info, lib, libexec, man and sbin. The directories libexec, share and var are intentionally missing there for reasons explained later.
Bootstrapping
Bootstrapping means, to initially create the /cw filesystem hierarchy, install RPM (the tool on which all depends) into it, create an initial RPM database for the /cw filesystem hierarchy and making sure that from then on the /cw filesystem hierarchy is controlled by RPM. This even means that RPM installs itself into its own database and manages its own installation (as a result, one even can upgrade RPM with RPM ;). To achieve all this, a special bootstrapping step is required before other software packages can be installed with RPM. Here we have two situations we have to distinguish:
- The machine has development tools installed.
This is the required prerequisite...
- if you build the packaging system from
scratch on a new Unix flavor for which still no binary bootstrapping
package exists or
- if you have a full-featured vendor installation
and want to add the packaging system by just building from source
(instead of installing pre-built binaries which could cause
trouble because of slight differences between the build and install
machines) or
- if existing binary packages were built for different root directories and/or owner uid/gid.
If this is the case, perform the following steps:
- Download the latest RPM bootstrapping source package from the
package repository (it is named
openpkg-0.9-N.src.sh) onto the target
machine.
- Make sure the following tools are already provided by
your vendor installation and are in your
$PATH: sh, uudecode, uncompress,
tar, gzip, gmake (or make if
it is GNU make), patch and gcc (or cc
if it is the GNU C/C++ compiler). If you have a modern Unix
operating system, an Open-Source development environment and a
reasonable shell environment this should be the case anyway.
- Execute the bootstrap command (as a regular user inside an abitrary
temporary directory):
$ sh openpkg-0.9-N.src.sh --prefix=/cw [--user=cw] [--group=cw]\The user and group you specify are the uid/gid which will own the hierarchy. If left out, the current uid/gid of the caller is used.
Keep in mind that until now access to the real target directory /cw was still NOT required. Nothing was actually touched on the system, only three other files were rolled as the result:
- openpkg-0.9-N.arch-os-id.sh
This is the bootstrapping binary package. This can be used in a second step (as described below under "The machine has NO development tools installed.") to initially create the target /cw. - openpkg-0.9-N.arch-os-id.rpm
This is the upgrading binary package. This can be used to upgrade an already created /cw hierarchy (on a different machine) or to later fix the existing /cw hierarchy (on the current machine) by running "/cw/bin/rpm -Uvh --force" on it. - openpkg-0.9-N.src.rpm
This is the upgrading source package. This can be used to install the RPM bootstrapping package sources in order to rebuild again -- but this time by using the already installed RPM.
So, to finally create the /cw hierarchy and link it into the system (by creating the owner uid/gid, by activating ts irc scripts and its cron jobs), execute (as root if you used --user/--group options before):
$ sh openpkg-0.9-N.arch-os-id.sh - if you build the packaging system from
scratch on a new Unix flavor for which still no binary bootstrapping
package exists or
- The machine has NO development tools installed.
This is the situation..
- if you have a brand-new machine where only a
base Unix operation system is installed (no development tools) but
for which an existing binary bootstrap package exists or
- if you want to quickly establish the packaging system onto an existing machine by accepting that using pre-build binaries can be not optimal.
If this is the case, perform the following steps:
- Download the latest RPM bootstrapping binary package from the
package repository (it is named
openpkg-0.9-N.arch-os-id.sh)
onto the target machine.
- Make sure the following tools are already provided by
your vendor installation and are in your $PATH: sh,
uudecode, uncompress and tar. If
you have a modern Unix operating system and a reasonable shell
environment this should be the case anyway.
- Execute the bootstrap command:
$ sh openpkg-0.9-N.arch-os-id.sh
- if you have a brand-new machine where only a
base Unix operation system is installed (no development tools) but
for which an existing binary bootstrap package exists or
Initial Filesystem Hierarchy
After installing the RPM binary bootstrap package, the /cw filesystem hierarchy looks exactly like this:
+-Basenames
|-Conflictname
|-Group
+-README |-Name
| +-DB/------|-Packages
| |-PKG/ |-Providename
|-RPM/----|-SRC/ |-Requirename
| +-TMP/ +-Triggername
|
|-bin/----+-rpm
| +-rpm2cpio
|-sbin/---+-lsync
| +-rpmtool
|
| +-rc
|-etc/----|-rc.env +-pubring.gpg
| |-rc.d/ |-rpmdev.mk
| +-rpm/-----|-rpmmacros
| +-rpmrc
|
| +-find-provides
| |-find-requires
| |-macros
| |-rpm
| |-rpmb
| |-rpmdb
|-lib/----+-rpm/-----|-rpme
| |-rpmi
| +-man1/ |-rpmk
| |-man2/ |-rpmpopt-4.0
| |-man3/ |-rpmq
/cw/-| |-man4/ |-rpmt
| |-man5/ |-rpmu
|-man/----|-man6/ +-rpmv
| |-man7/
| +-man8/----+-lsync.8
| |-rpm.8
|-include/ |-rpm2cpio.8
|-info/ +-rpmtool.8
|-libexec/
|-share/
|-var/
| +-README
| |-PKG/
| |-bin/ +-man1/
+-local/--|-sbin/ |-man2/
|-etc/ |-man3/
|-include/ |-man4/
|-info/ |-man5/
|-lib/ |-man6/
+-man/-----|-man7/
+-man8/
As you can see, it's the directory structure described above plus the
first package (RPM) already installed. Additionally you can see that
under /cw/RPM/ an RPM-specific area exists. There is the RPM
database, that is, the whole filesystem hierarchy is self-contained
because it contains its own database and packaging tool.
Package Management
If the /cw hierarchy was bootstrapped, one can start managing packages for it. The following common tasks give you a very short overview of the most essential RPM commands:- Query Information
$ rpm -qa
(q)uery list of (a)ll installed packages$ rpm -qi foo
(q)uery (i)nformation about package "foo"$ rpm -qvl foo
(q)uery (v)erbose file (l)ist of package "foo"$ rpm -qpi /path/to/foo-X.X-X.XXX-XXXX-XX.rpm
(q)uery (p)package file for (i)nformation$ rpm -qpvl /path/to/foo-X.X-X.XXX-XXXX-XX.rpm
(q)uery (p)package file for (v)erbose file (l)ist - Install or Upgrade a Package
$ rpm -Uvh /path/to/foo-X.X-X.XXX-XXXX.rpm
smart (u)pgrade while (v)erbosely showing (h)ash characters - Verify a Package
$ rpm -V foo
(v)erify integrity of package "foo" - Erase a Package
$ rpm -e foo
(e)erase package "foo"
For more details on the really sophisticated RPM command and its numerious functions, please consult the book Maximum RPM, which we also provide online for your convinience.
Notice that the /path/to/foo-X.X-X.XXX-XXXX.rpm in the above commands can even be a fully-qualified URL with the FTP and HTTP schemes. So, with RPM you even can directly install or upgrade a package from the package repository by prefixing the filename listed there with http://www.openpkg.org/pkg/. For instance to easily upgrade the RPM installation, just run
rpm -Uvh http://www.openpkg.org/pkg/rpm-4.0-X.XXX-XXXXX.rpm
(replace the X characters with the latest release number and the architecture and operation system id) #
The local/ Area
# # We still have to explain the /cw/local area, which, as already said # above, is intentionally not RPM managed and intended for manual # installation of software packages local to the particular machine. The # RPM bootstrap package created just the top-level directories for this # area and a tool /cw/sbin/lsync (for "local sync"). But what is # special on this area? # ## ... @ 1.1 log @Initial revision @ text @d12 1 a12 1 href="doc/maximum-rpm/index.html">Maximum RPM, which we also provide @ 1.1.1.1 log @Import www.openpkg.org website @ text @@