Seth, this is a great idea. I'm wondering: Whenever I rollout a new release, I'm constantly plagued with "Awwww crap! forgot to install <group/package name>", or install something, but later on down the road, no longer want that package on the system (compile/install from source, etc). Thinking aloud, unwise at 6AM. 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" Hmmm, this does nothing to help with your syntax question, but I felt a neuron fire for once, and had to capitalize on it. Feel free to rip this apart! Cheers, e. -- e r i k w i l l i a m s o n erik@xxxxxxxxxxxxxxxx system admin . department of computer science . university of calgary -----Original Message----- From: yum-admin@xxxxxxxxxxxxxxxxxxxx [mailto:yum-admin@xxxxxxxxxxxxxxxxxxxx]On Behalf Of seth vidal Sent: May 28, 2003 11:36 PM To: yum@xxxxxxxxxxxxxx Subject: [Yum] script run idea Hi everyone, something I've been wanting to play with some: yum scriptaction (or some such word, I don't know yet) filename/url so it would either read or download a file from a url then do what the file says. This part is easy - I was trying to figure out the niceties for internal syntax of the file. I thought of something like this: installgroup Groupname updategroup Groupname remove pkgname install pkgname update pkgname # comment ; comment one item per line but then I thought, that would make the file format maybe a touch too similar to the commandline arguments and maybe confusing so I thought - why not make it like %packages in ks.cfg @groupname packagename -packagename -@groupname but that wouldn't make any room for updating operations either and I've kinda never liked the @ syntax for groups - I know it's common to netgroups and other things but it's not flipping obvious to me. The idea behind this would be that yum would parse this file and treat the actions requested as a single transaction. you could, of course, do this with multiple yum commands in a shell script, but that would incur a lot of startup/shutdown time and in general not let you do a lot of things that are consistent to do at one time at once. Ideas on better syntax? I think xml might be a tad overkill for this operation. -sv _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxxxxx https://lists.dulug.duke.edu/mailman/listinfo/yum