On Mar 6, 6:02 am, Bruce Richardson <itsbr...@workshy.org> wrote:
> You have a choice of altering the third party code or your own. You
> will keep encountering this problem if you use third party modules. I
> guess you could do create your own safe package wrapper, something like
> this:
>
> define safepackage ( $ensure = present ) {
> if !defined(Package[$title]) {
> package { $title: ensure => $ensure }
> }
>
> }
>
> And either use it everywhere (not necessarily a good idea) or wherever
> you hit a problem with third party code.
I'd recommend *not* using such a wrapper at all, mainly because
testing for resource definitions via the defined() function introduces
a parse-order dependency.
If you decide to use such a wrapper anyway, then you should use it
absolutely everywhere, including updating all third-party modules you
employ. I think it's better, though, to just let the compilation
failures happen -- use them to detect where you need to patch up
conflicts between modules.
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.
