Re: [Maxlinux-devel] New Basesystem

[Kelledin <kel...@sk...>]

On Wednesday 21 August 2002 02:30 am, Enrico Kern wrote:
> First, i need a running base-set for the setup-cd, so i
> created one (list from previous mail). This works fine, is
> standard and fully conform (installation fits LSB). Sure i
> install the rpms, but not the basesystem. If you whish i do
> that, but ill find it heavy.. i have only a big fat list of
> RPMS.. i must find and sort out the depencies of all libraries
> needed by the base-system, sure rpm can check and install
> depencies, but with a own maintained basetree, we drive better
> imho. We can also convert this "own" base to a "base.rpm" or
> somewhat.. i see no problems, but a better managment of the
> installation.

Sorry about the one big fat list...I've attached a script that=20
may help you along with that.  It's capable of taking a=20
directory full of RPMs and generating a list of dependencies=20
between those RPMs.  It's 99% effective, which may be good=20
enough for a quick job.  Its main limitations are that it won't=20
actually check version numbers of provided symbols, and it=20
prefers to leave out dependencies that rpm sticks in there just=20
for the hell of it--dependencies like rpmlib(blah,blah).

Instructions for use:

Take all the RPMs in the big fat list and place them in a single=20
directory.  There should be nothing else in this directory, not=20
even child directories.

Run "./gendlist.sh [rpm-dir] > rpm-dep-list".

You should now have a depmod-style listing of RPM dependencies.

Just to get you started, I've attached an example list of=20
dependencies.  I generated it using the following commands:

mkdir RPMS
cp /mnt/smb/Midgard/ftp/LATEST/RPMS/{i486,noarch}/* RPMS/
=2E/gendlist.sh RPMS > rpm-dep-list.example

--
Kelledin
"If a server crashes in a server farm and no one pings it, does=20
it still cost four figures to fix?"