Mayank <mail2may...@gmail.com> writes:
> On Sun, Apr 18, 2010 at 6:18 PM, Peter Meier <peter.me...@immerda.ch> wrote:
>> > Now I am able to get puppet work for me in very first run. I had to do a
>> > require => Exec["updateyum"] for every package installation in order to
>> > ensure that the command yum update -y ran before package is being
>> > installed. However this brings me to my initial question. Since I'd
>> > mentioned exec{"updateyum": ....} before any package statement so had
>> > puppet some way of ensuring serial execution of script I would have been
>> > saved from mentioning it every time in package statements.
>>
>> you can shorten that by either wrap your package installation with a define,
>> or define at the top:
>>
>> Package{ require => Exec["updateyum"] }
>>
>> which will introduce a global dependency on the Package resource on that
>> exec. Note: afair if you set another dependency you will have to reset
>> it. But it looks like this will be once for your setup.
>
> Thanks I'll wrap it up with a define and check it out again. Thanks to
> everyone for valuable advises. I guess I'll be creating some better recipes
> in coming days thanks to these advises :)
I would strongly advise that you use the global dependency, since that avoids
the need to have a non-standard define that acts almost like the standard
package resource.
If you have packages that you require before the package manager update, just
declare them with an explicit empty 'require' attribute and you will override
the global dependency.
Daniel
--
✣ Daniel Pittman ✉ dan...@rimspace.net ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.
