On Tue, Oct 5, 2010 at 12:16 AM, ncantor wrote:
> However, by default, the package isn't called by anything.
There's also a subtle shift in thinking that may help you work with
puppet. In the puppet language, resources are "declared" rather than
"called" It's a bit strange because many resource
On Tue, Oct 5, 2010 at 12:16 AM, ncantor wrote:
> For some reason, puppet is attempting to install ruby-enterprise on
> all my puppet clients.
You told puppet to do so. =) I don't mean to be a jerk, but this
really is the simple answer.
> The only reason I can find for this behaviour
> is that
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
For some reason, puppet is attempting to install ruby-enterprise on
all my puppet clients. The only reason I can find for this behaviour
is that I've defined a package to install ruby-enterprise. However, by
default, the package isn't called by anything.
In order to get the package to only install
For some reason, puppet is attempting to install ruby-enterprise on
all my puppet clients. The only reason I can find for this behaviour
is that I've defined a package to install ruby-enterprise. However, by
default, the package isn't called by anything.
In order to get the package to only install
