On Tuesday, June 30, 2009 6:22:26 PM UTC-4, lutter wrote: > > > The basic issue is that puppet doesn't know about dependencies (not sure > it should), but once you throw 'yum -y erase' into the mix, it becomes > very easy to write inconsistent manifests, where a package erase removes > a package that is explicitly mentioned by the manifest for install - > sure the next puppet run will then install that package again, but in > the meantime, you have a very broken system as the 'yum erase file' > example shows. > > I don't buy it. I would MUCH rather have puppet go all cyclical like that than not have any decent way to remove packages. At least if I saw that behavior, I could intervene and make things better. Instead I can't make things work at all short of creating my own definition which just wraps an exec of "yum -y remove $name" anyway. If someone really wants the super conservative behavior, let them use the 'rpm' provider, but lets make the 'yum' provider do what yum was intended to do in the first place, manage dependencies!
-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
