On Tue, Oct 05, 2010 at 12:16:28AM -0700, ncantor wrote:
> In order to get the package to only install on the systems that I
> wanted to have it, I had to move it from a general package definition
> to be inside a class. Is this normal behaviour?
Yes. If you do want packages to be visible at the top level, to
absolutely everything, but only installed when you want them, then you
should make them virtual resources and then realize them where you need
them.
What is your motive for defining packages at the top level? As with
most resources, it's usually better to define them within the
classes/modules which need them and just include the class. This allows
you to concentrate on high level function (e.g. "This node should get
its user and group data from an ldap server at $uri") in your main
config and keep the low level details ("On Debian, the nss_ldap config
file is '/etc/libnss-ldap.conf'") hidden within the module.
--
Bruce
I object to intellect without discipline. I object to power without
constructive purpose. -- Spock
--
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.
