Ah, thanks! I remember reading about this somewhere in the mailing archives. So yumgroups.xml would just be placed in the same directory as the rpms or in the header directory? Cool, thanks! That helps out a lot. That makes it really easy for me to make a webpage on the server which can add rpms to the "required" category. We basically have patches that get delivered to computers. The whole process needs to be automated. This solves a key problem. I will search through the mailing archives about yumgroups. Thanks! Mark > > You can accomplish what you are trying to do (group systems) by editing the > yum anacron file: /etc/cron.daily/yum.cron > > If you setup some groups (ala yumgroups.xml) on the server, and then add an > entry to your yum.cron file on the client, the client will always have the > packages listed in that group installed - provided you have nightly yum > updates enabled. > > EX: if you call your group 'foo' in your yumgroups.xml, then add a line like > the following to your yum.cron on the client: > /usr/bin/yum -e 0 -d 0 -y groupupdate foo > > -Jeff > > On 7/15/04 7:22 AM, "mark_yum@xxxxxxxxxxx" <mark_yum@xxxxxxxxxxx> wrote: > > > > > Yeah, without actually typing in > > yum install PACKAGE > > how do you get yum to install required packages? > > I think the RHN network tells the clients which packages they need to install > > and then they install them. Can this be done with yum without anymore > > scripting on the client side? > > Updates are easy, but for rpms that are new, it seems like you have to > > manually > > run yum. > > I can get around this, but that would be one plus for RHN, unfortunately. > > Thanks! > > Mark > > > > > > _______________________________________________ > > Yum mailing list > > Yum@xxxxxxxxxxxxxxxxxxxx > > https://lists.dulug.duke.edu/mailman/listinfo/yum > > > _______________________________________________ > Yum mailing list > Yum@xxxxxxxxxxxxxxxxxxxx > https://lists.dulug.duke.edu/mailman/listinfo/yum >
