Hi Brian,
> > Wow! Only 106 packages.
>
>Yup. And like I said, that was with really no effort (in paring down)
>which means it is likely too much.
>
> > My development machine has over 500 packages and,
> > no, I don't know what they all are.
>
>So I am 20% of what you have installed, so likely <20% of all packages
>on a 7.2 install CD. I really don't want to download 5x the packages
>I will actually install.
For laughs, at one point I saved the result of "ls -lR" for each of the 7
CD's in my 7.2 distribution. Install CD #1 has 929 packages and #2 has 734
packages. So my development machine has only 1/3 of the available
packages. My firewall machine has 211 packages, which includes perl,
python, gcc, apache, etc, etc. Undoubtedly both machines could be trimmed
down ...
Given your 106 packages vs. the 1763 of the distribution you're at the
15-16% installed level.
> > One strategy might be to create a script that uses the rpm list that "rpm
> > -qa" generates, trims the package names of version info, then uses
> rsync to
> > update a selective mirror site. At the very least, that would produce
> > something close to the proper set of packages needed and would
> > significantly cut down on disk usage. Given the downloaded packages, the
> > script could then be used to determine additional dependencies and get
> them
> > or notify you of their need.
>
>Yeah, I before MandrakeUpdate I had written one of those, and I could
>dig it up and resurrect it but I really think this is something that
>Mandrake NEEDS in the distro. That is why I suggested it.
Obviously you're ahead of me on the project! That's the way it should
be. Another tool comes to mind - RPMFIND which has the ability to find
package updates and resolve dependencies. It might be a solution for you.
David
--------------------------------------------------------
David Relson Osage Software Systems, Inc.
[EMAIL PROTECTED] Ann Arbor, MI 48103
www.osagesoftware.com tel: 734.821.8800
