On Thu, 2003-08-14 at 08:30, Steve Traylen wrote: > This may be of use to someone else so here it is, its not > very clever but is useful > > http://hepunx.rl.ac.uk/~traylens/rpms/yumit > or > /afs/rl.ac.uk/user/t/traylens/public_html/rpms/yumit > > contains > > yumit-1.2-2.src.rpm > yumit-client-1.2-2.noarch.rpm > yumit-server-1.2-2.noarch.rpm > > The client effectivly runs > > `yum update` to get a list of packages that should be upgraded > and stores all of this output in a central mysql database. > > The server portion is just php scripts to browse all your hosts and > rpms to see what rpms should be installed where. > > I suppose this generates a request from me. > > While `yum update` is great at generating a list of what should be installed > what are the chances of `yum outofdate` or something that would generate a list > of all packges with their versions that would be upgraded or removed if I was > ran `yum -y update`. 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? -sv
