RPJD says: > and this might be related to the "group" feature of yum of which i > have no idea, and which is not documented in the man page. In my understanding of the group feature, it works more like the Red Hat installer itself where you can pick groups of packages by a generic description. Say you pick "Web Server", it will not only install apache but also a lot of the complimentary packages that one might find handy to have on a web server. The feature is documented, but unfortunately not in a central or obvious place. I learned about it mostly by combing through the archives of this mailing list, starting approximately in June, IIRC. It uses a subset of the same XML DTD that is used by Red Hat in comps.xml on the install disc. Basically you can group a bunch of packages together and do something like "yum groupinstall dept-trainers" and all of the packages that I've assembled for the documentation department standard build will get downloaded & installed. You don't need to run a yum-arch after creating a yumgroups.xml. You can put the yumgroups.xml in any of your repositories. Yum will look for yumgroups.xml in each of the defined repositories, and will concatinate all of the defined groups if it finds more than one yumgroups.xml. yumgroups.xml goes in the base directory of the repository. I basically have two yumgroups.xml files; one is just a renamed copy of comps.xml and is installed in my Red Hat base repository, and the other is company specific in my company repository. The company yumgroups.xml can contain groups for departments to make it easy to have a standard host configuration for each department, and also has some company-wide mandatory packages. Now here's something I haven't tried... can you nest groups? That is to say, if I have a generic group called "Graphics Software", can I set up a department group that includes the group "Graphics Software" plus individually named packages? (which would certainly simplify my company config even further still) --Magnus
