Why not use "up2date" then... *snicker*
You know, I have this same gripe. Yes the "rpm -Fvh {package}" only installs the latest version in the dir, not sequentially run through them. Only problem is the updates that have to be "Upgraded vs. Freshened" or when they change the break-out of individual pieces to help with maintenance (see recent Perl 5.6.1 fubars in bugzilla for recent gripes and explanations)
My solution so far:
From my "local" psuedo-mirror for distros I support
cd ~ftp/pub/redhat-7.2/updates/
wget -m -nh --cut-dirs=3 [link|ftp://closest.mirror.updates.redhat.com/7.2/en/os/|ftp://closest.mirr...m/7.2/en/os/]
I then have a "deprecated" directory in every "arch" dir, which has chmod 700 on the dir. I then, just ls, then move old junk to "deprecated".
One thing I have yet to do, is actually update the installation so I don't have to update newly installed machines. This is a "|DREAM" for now.
It is a PITA, but well I haven't even looked. Of course the stock answer I get from "everyone", "Use up2date"... yeah Right! I would rather be behind current on Production machine than to "auto-magically" install stuff and break things(like the recent "oops, we forgot to list mod_perl" incident).
And, yes, I shall be looking for somehting... yes the naming convention isn't good right now, but I see a standard forming as of late.
greg, curley95@attbi.com -- REMEMBER ED CURRY!!!
Keep software free. Oppose the CBDTPA. Kill S.2048 dead.
[link|http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html|[link|http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html|http://www.eff.org/...a_alert.html]]