> > I think this is even more important when you have a lot of churn. > > Simply being able to flip between versions of the packages quickly > > will surely save an awful lot of time. > > What he said - really. Three immediate benefits: > > - having the build process entirely scripted in the spec file ensures a > consistent build process over time. > > - the first time you deploy a new version that explodes, rolling back to a > set > of known good binaries is utterly trivial to do in moments. > > - as sensitive boxes (security monitors) it's very useful to be able to > easily > verify the software binaries, using either the local rpm database or a copy of > the original rpm. for a little extra, you can pgp sign your rpm files too. >
OK, OK :) I know this and agree with it in principle. It is just that at the moment I am extremely hard pressed and really don't have the time to work my way through figuring out how to build rpms from scratch. The package Daniel pointed out looks very promising in this respect adn I will certainly look at it. I'll repeat the question from my previous post: Is there a straight forward way to have a local rpm repository on the puppet server rather than relying on yum and the RHE channels? Thanks, Russell -- 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.
