> You don't tell us how wget::fetch is implemented so I can only guess > that there is an exec resource in there? The wget::fetch resource is > *always* evaluated so you have to make sure that the exec resource inside > does not do anything (the exec resource has a `creates` parameter you > can point to a file. If this file is present the command specified by > the `command´ parameter will not run). > > The wget package is: http://forge.puppetlabs.com/maestrodev/wget The archive package is: http://forge.puppetlabs.com/bobsh/archive
> Is there a reason why you do not install python as a package or build a > package your own? > > I wanted a python class where I could declare the version I wanted and have it download and make-d. Most the package management systems I've seen come with 2.6 (or older!) by default. I didn't want to create my own package for reasons I listed in another email: extra complication (python is really easy to make from source) and extra maintenance (would have to maintain different python versions for every package management system I wanted to support). I really just wanted to create a simple puppet script to download and install python in a consistent fashion on whatever system I happened to be setting up. -dave -- 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.
