up2date behaviour

So after the new updates hit, I still had the glibc and -common prolems 
with the amd_64 channel, but as was suggested before the Sept. 12 updates, 
I pulled up2date first, and then the other updates came along just fine in 
the next run.

Perhaps up2date should have this behaviour built-in (or at least 
configurable)?  I've noticed that an automatic update tool from a certain 
Redmond, WA based company does try to update itself first before 
attempting to update the system.

I can see cases where it may be undesirable to update up2date, but not
many.  Maybe if up2date has been in structed to get all updates, AND there
is new version of up2date available, then it should update itself first
before trying the other rpms.  I guess that would be easy enough to script 
by the local admin, but it seems a sensible default behviour.

if [ `up2date -l --nox | grep up2date ` ]; then up2date -u --nox up2date; 
fi ; update -u --nox






-- 
Ryan Sweet <[email protected]>
Atos Origin Engineering Services
http://www.aoes.nl


--
Taroon-beta-list mailing list
[email protected]
http://www.redhat.com/mailman/listinfo/taroon-beta-list