> Could this be used as a method to do a sort of 'system check'? Hmmm, almost > like the package selection in a kickstart config, but with removes, etc. It > would need to accept the fact that some (most) packages may already exist, > some that are tagged for removal may not be on the system... A sort of > 'template' for the system. It could be helpful for those of use whose > systems evolve a fair bit over the course of the roll-out. > > yum -c http://path/to/yum.conf -t http://path/to/yum.systemplate <action> > > You'd need a whizzy action name that says "make me like this template file > says" I don't want to add an option that points to the template b/c that would defeat the purpose of the "whizzy action name" it would need to be more like yum -c conffile templatematch url://path/to/template -sv
