On Wed, Jul 21, 2004, Simon J Mudd wrote:
Re Simon,
> I'm using Whitebox Linux (a RedHat Enterprise 3 clone) [...]
>
If you know better than rpm that a binary package can be used on a
particular system or you just want to give it a try then convince rpm
using the --ignoreos or --ignorearch options. The situation you are
describing sounds promising when ix86-rhel3 binaries are used.
> 2. After building and executing [...]
> However this whole process is manual [...]
> I've since seen that there is openpkg-index and openpkg-build [...]
>
First install the openpkg-tools package. It requires make, gcc and perl.
Having only the bootstrap available the whole thing can be setup using
$ openpkg install openpkg-tools
With the tools being installed use something like
$ openpkg build apache | sh
The "build" tool reads the indices from the OpenPKG ftp server based on
the bootstrap you're using, takes package options as arguments, computes
the dependency chain and writes the commands you would have to enter
manually to stdout. The example above directly pipes these commands into
the shell. Try these and learn:
$ openpkg build apache
$ openpkg build -D with_mod_ssl=yes apache
$ openpkg man build
> I'd like to keep OpenPKG uptodate. [...]
>
Frequently run
$ openpkg build -Ua | sh
Be aware that updates for release are created very carefully and in
almost all cases they can be applied and everything will continue to
work. In contrast, if you run CURRENT then every update can completely
change world order ... You find two paragraphs describing this at the
top of the Release Notes below "General Notes about Upgrading".
[1] http://cvs.openpkg.org/openpkg-re/releasenotes.txt
--
[EMAIL PROTECTED], Cable & Wireless
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
