> > I like your idea here; reason being that with my local system, each host > here uses yum twice - one config for the redhat release and it's updates > (using "yum -c http://blarg update"), and one for 'extras', like select > freshrpm packages, and whatever else people ask for once I do the > rollout (using " yum -c http://foo install \* "). Looks like this could > take care of that. but how do I parse those for the purposes of one transaction? an example: install foo -c config1 install bar -c config2 install baz -c config3 now - if I want those handled as one transaction, I'm going to have to read config1, figure out where to get foo and its deps, then read config2 and do the same for bar but how do I finish the process? ie: once I know all the steps I will need I'm not done with the config information. I need the config info to know where files are. But if you're saying you handle everything up to a -c in one transaction, then restart for a second config file, that's a different story. so something more like this: config /path/to/config install foo update bar remove baz groupinstall quux config /path/to/config2 install do remove re update mi groupinstall fa config /path/to/config3 install tom remove harry update john that would be more doable - in 3 separate transactions -sv > > I agree with Troy about the syntax; the command-line syntax is great. > > e. >
