On Sun, 2004-06-06 at 22:39, Michael Weiner wrote: > On Sun, 2004-06-06 at 15:34 +0100, Jon Peatfield wrote: > > I make use of a handy repostory maintenance script (rh_buildtree > > written by Peter Benie who works in a different department here), > > which given a set of directories full of rpms constructs/maintains a > > directory which contains the latest version of all those packages > > which pass a signature-check (as hard-links to whichever source they > > were from -- original shipped version, updates, local-packages etc). > > > > [ We use it to re-build install trees overnight so that a fresh > > install always goes straight to having the latest versions available > > from the tree (which saves having insecure versions until patched and > > also is much quicker). > > > > We also use a script (rpmalert) which checks what versions are > > out-of-date on a machine and another (rpm-update) which applies the > > updates we have flagged as ok, but I suppose you may have yum/up2date > > for that function anyway. ] > > > > I'm still using this older repository maintenance script for my redhat > > trees (which takes ~15 minutes to run and (I think) results in an > > extra copy of some of the packages on disk). > > > > As part of my experiments with Suse9 I tried Peter's new repository > > maintenance script (rpmstream) which usually runs in seconds (since it > > keeps more cache info around). > > > > If you just want the latest versions of update packages that could > > probably be done easily enough. > > > > and are ANY of these scripts available publically, or anything CLOSE? > I would be interested in these scripts too -- -- fedora-legacy-list@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-legacy-list
