Background: I have hunch that the weird behavior where $1 == 0 in rpm
scripts on *upgrade* in some cases (causing all sorts of brokenness when it
happens) is related to transactions which involve kernel upgrades, and
specifically because those transactions involve installonlypkgs.
To help test this theory and also as a workaround in case I'm right, I'd
like to change our auto-update cron script to run `yum update
{installonlypkgs}` before the general `yum update` command. I could of
course hardcode a list of things for {installonlypkgs}, but it seemed nicer
to query for it.
Is there a particular reason the yum shell 'config' command only accepts a
certain subset of config values? Could "installonlypkgs" be added to that
list? That'd be handy.
Or, is there some other way I'm missing? Thanks!
--
Matthew Miller mattdm@xxxxxxxxxx <http://mattdm.org/>
Boston University Linux ------> <http://linux.bu.edu/>
_______________________________________________
Yum mailing list
Yum@xxxxxxxxxxxxxxxxxxxx
https://lists.dulug.duke.edu/mailman/listinfo/yum
