With regards to yum-cron, I just wanted make a couple of comments.
I have always replaced the default yum-cron update script with one that
has several groupinstall calls. I have several local package groups
which I maintain, and if I need to add a package to a certain class of
machines, I just add it to the groups.xml file.
This causes two problems:
With the yum in F17 and the one that was pushed as an update to F16,
there's no provided mechanism to override the yum scripts. They're in
/usr/share and aren't marked as configuration files, so changes get
wiped out.
I hacked around this by sticking this in /etc/sysconfig/yum-cron:
SCRIPTDIR=/etc/yum-cron
YUMSCRIPT=${SCRIPTDIR}/${ACTION}.yum
then copying everything from /usr/share/yum-cron to /etc/yum-cron
and editing the file I need to change.
This does work fine. Unfortunately it also causes yum-cron to spam me
nightly because there are errors that yum produces even when run
quietly. The messages are of the following two types:
Warning: Group arabic-support does not have any packages.
Package ibus-m17n-1.3.3-11.fc17.x86_64 already installed and latest version
And arabic-support definitely has packages, though they're all already
installed. When yum-cron was a separate package, I just patched the
script to grep these out.
So, some questions:
Is there a better way to keep everything in a group installed
automatically without having to go through this?
If not, please consider a reasonable override mechanism in yum-cron, and
perhaps a way to eliminate excess verbosity from yum.
- J<
_______________________________________________
Yum-devel mailing list
[email protected]
http://lists.baseurl.org/mailman/listinfo/yum-devel
