Hi Thomas,
Thomas Lotterer <[EMAIL PROTECTED]> writes:
> On Wed, Jul 21, 2004, Simon J Mudd wrote:
>
> > 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.
OK. I was not aware that this was possible. Certainly the rpm --force
command was completely ignored.
I also tried to adjust the shtool included in the original bootstrap
tar image to recognise whitebox linux as rhel3.
--- shtool.orig 2004-07-22 20:37:04.000000000 +0200
+++ shtool 2004-07-22 15:55:01.000000000 +0200
@@ -2713,6 +2713,9 @@
slackware ) n="Slackware[ Linux]" ;;
turbolinux ) n="TurboLinux" ;;
unitedlinux ) n="UnitedLinux" ;;
+####
+ whitebox ) n="<R>ed <H>at <E>nterprise <L>inux" ;;
+####
* ) n="${n}[ GNU/Linux]" ;;
esac
case "$n" in
producing the following 2 files:
-rw-r--r-- 1 root root 6051007 Jul 22 16:02
openpkg-2.1.0-2.1.0.ix86-rhel3.0-ope.rpm
-rw-r--r-- 1 root root 6301696 Jul 22 16:02
openpkg-2.1.0-2.1.0.ix86-rhel3.0-ope.sh
This installed correctly but downloading the binary rhel3 packages
gave me an error inspite of the change (I guess I need to change other
things (in rpm?) too.
[EMAIL PROTECTED] PKG]# /openpkg/bin/openpkg rpm -Uvh
ncftp-3.1.8-2.1.0.ix86-rhel3-openpkg.rpm
Preparing...
########################################### [100%]
package ncftp-3.1.8-2.1.0 is intended for a rhel3 operating system
[EMAIL PROTECTED] PKG]# echo $?
1
> > 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 either missed this on the web page or it's not clearly enough
explained. This is great (I've just tried it), and very similar to
FreeBSD's ports system.
> > I'd like to keep OpenPKG uptodate. [...]
> >
> Frequently run
>
> $ openpkg build -Ua | sh
OK. This is what I was missing. I must have missed it from the web
site. I need to look again to see why I did that.
> 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".
OK. That is logical, and similar to other OS' "current" versus
"release"/"stable" packages.
Thank you for the pointers. I feel a bit dumb for not having seen them
before.
Simon
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
