On Jan 17, 3:11 am, Steve Shipway <s.ship...@auckland.ac.nz> wrote:
> You can make the package resource definition conditional.
>
> class foo {
> if ! defined( Package[gcc] ) {
> package { gcc: ensure=>installed; }
> }}
>
> class bar {
> if ! defined( Package[gcc] ) {
> package { gcc: ensure=>installed; }
> }
>
> }
>
> Or, define a new class for the package(s) and include that
>
> class pkg::gcc {
> package { gcc: ensure=>installed; }}
>
> class foo {
> include pkg::gcc}
>
> class bar {
> include pkg::gcc
>
> }
>
> Second method is more elegant IMHO; but if its a one-off then first might be
> simpler.
The first is simpler only if you get lucky, and you don't intend to
modify your manifests ever again. Use of the "defined" function
introduces a parse-order dependency, and the additional work you need
to do to ensure that that dependency is always fulfilled overcomes any
simplicity advantage that might otherwise exist.
If you don't do that work, correctly, then you may still luck into the
code working, but you risk in the future making some seemingly
unrelated change that breaks it.
All-in-all, I'm inclined to consider any use whatever of the 'defined'
function to be a kludge, and a shaky one at that.
John
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@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.
