> well, nothing will be removed with a yum -y update. Erasures won't > happen on an install/update request. It's just a nightmare to predict > when you'll get into an erasure cascade so update/install will never > arbitrarily erase a package unless a package obsoletes an installed one. > > > > It would useful to be able to browse the packages that are installed that > > should not be , hmmm guess I should learn some python. > > that 'should not be'. How do you determine if a package should not be > installed? Based on whether or not there is an update for it? By 'should not be' I mean the set of packages-versions which are currently on the system that would be altered by running `yum -y update`. So package-1.2-3.rpm should not be on the system since package-1.2-4.rpm is available. Also netscape-4.7-3.rpm should not be on the system since say mozilla-5.0.rpm 'Obsoletes:' in the .spec file netscape <= 4.7-3. (Not a very good example I know but hopefully you get the idea.). Steve Steve -- Steve Traylen s.traylen@xxxxxxxx http://www.gridpp.ac.uk/
