> class audio-video {
> # In this example we are not being picky about ordering of
> installation of libxine1-ffmpeg
> $packagelist = ["vlc", "amarok", "libxine1-ffmpeg"]
>
> package { $packagelist:
> ensure => installed,
> }
> }
>
> Although it is not operationally important I prefer the style of the
> first example (using require => Package) since I believe it enforces
> ordering, which in some cases may be very important. Is there
> something wrong with the definition in the first example? Does anyone
> have any idea why it doesn't work?
That's a very sound way of thinking as far as puppet is concerned, and
as already mentioned in the thread, you should both declare the package
and require it.
However, this is not an example in which you should enforce ordering.
The rule of thumb (for me) is to *only* enforce order if a resource will
not work unless its dependencies are met (e.g., you cannot have puppet
edit a config unless the owning package is already installed etc.).
As far as packages are concerned, those have excellent dependency
support of their own. If amarok doesn't depend on a lib, it doesn't make
much sense to invent such a dependency. At the end of your run, all your
packages *will* be present, so it shouldn't make any difference (edge
cases notwithstanding).
HTH,
Felix
--
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.
