On 19 Mag, 22:17, Peter Berghold <salty.cowd...@gmail.com> wrote: > On Wed, May 19, 2010 at 4:08 PM, Steven VanDevender <ste...@uoregon.edu>wrote: > > > P > > > You're probably going to be better off making custom RPM packages for > > things that you want to have locally-built, place them in a local > > repository that your systems are configured to access, and then using > > the Puppet "package" resource type to install them. > > I thought that as well, but didn't really want to just yet. > > If I go that route I guess it will mean I'll have to get around to doing > something I've been putting off.. I've been planning to build a custom yum > repository but that was not going to happen right way.
You might find interesting (also to see how to manage dependencies among different execs) the custom define I made to manage downloads of tarballs, extract and compilation / installation commands: netinstall define http://git.example42.com/?p=example42modules/.git;a=blob;f=common/manifests/defines/netinstall.pp an example of usage: http://git.example42.com/?p=example42modules/.git;a=blob_plain;f=mailscanner/manifests/classes/netinstall.pp Al -- 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.
