Usually creating a separate class is best, but for odd single packages
I'll add them to a single class as virtual resources.
oneoffpackages {
@package {'mysql-client'}
@package { 'perl-Getopt-Long-Descriptive': }
}
Then when I want to use that package I'll realize it.
nrpe::delllperc {
blah blah
realize Package['perl-Getopt-Long-Descriptive']
}
collectd::redis {
blah blah
realize Package['perl-Getopt-Long-Descriptive']
}
hostgroup::frontend {
blah blah
realize Package['mysql-client']
}
mysql {
blah blah
realize Package['mysql-client']
I'm not sure it's any cleaner or easier to maintain, but it's another
idea.
Ramin
On Jan 13, 9:02 am, bel <belm...@gmail.com> wrote:
> We have a database module and an application module that both require
> gcc. When I include both modules in a node, I get errors about the
> package being already defined.
>
> How would I address this?
--
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.
