Majority of the time rpm deps in fedora are good, so thats not that big of a concern. I am just overly anal about stuff where if I install the ldap client I also make sure pam is there also (yet you would expect the rpm dep to satisfy it).
Hmm, maybe you are misunderstanding me. The NTPD class/module has the required packages in there, but if my yum.conf is not setup or the class dependency is not defined for it then the pkg install will fail for obvious reasons. So the only way I know how to make every one of my modules (I have over a dozen of them now) that install packages is to make sure they have a direct dependency on the yum class/module to run before. What I want to do is enforce a global dependency perhaps, or a way of ensure that yum is the very first thing that gets setup on my system before any other module is run due to the direct dependency on a proper yum.conf. Make sense now? Because of this direct dependency and no proper ordering with puppet without it, I have to sometimes to do two puppet runs. -Chris On Thu, Mar 18, 2010 at 10:14 AM, Michael DeHaan <mich...@reductivelabs.com>wrote: > On Thu, Mar 18, 2010 at 10:03 AM, Christopher Johnston > <chjoh...@gmail.com> wrote: > > Being able to install yum groups would be a nice value add. Sucks having > to > > list out 8-9 packages and hope rpm/yum deps get sorted out. But what I > am > > really griping about though is something like this. > > Well, if the packages *do* have proper dependencies, installing one > will install the dependencies. I would hope there's no hoping on > that, though it may be you have packages that don't have good > dependencies yet. In that case, fix the packages and that problem > goes away :) > > > > Say you have 2 modules, one called ntpd and one called snmpd. Two > totally > > different types of configurations because not every system might get ntpd > > configured (only my DNS servers do). In each of my manifests they have > to > > install packages, but both modules have a direct dependency on my yum > module > > to have been run and successfully setup in order to get packages from the > > right repo. It gets a little out of control to have to remember to put a > > require for the yum module every time I call a package type. > > Modelling it as a "yum module" seems a little weird to me (though I > can see where it would save typing in fairly homogenous environments), > I'd think it might work better if you keep the package requirements > inside the modules that need them. That is to say, if you have an > NTP class/module, require the packages needed for NTP there? > > --Michael > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com<puppet-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
