I find it confusing that Puppet defines modules as reusable code yet,
when it comes to packages, you have to have prior knowledge of what
other package resources are defined.
Thank you for all the proposed solutions but does anyone know if
Puppet has a best practice they recommend in this case? Otherwise, I'm
going with defining new classes for the packages.
On Jan 17, 4: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.
>
> Steve
>
> Steve Shipway
> University of Auckland ITS
> UNIX Systems Design Lead
> s.ship...@auckland.ac.nz
> Ph: +64 9 373 7599 ext 86487
--
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.
