Thanks for posting the code snippet. We haven't been building RPMs for internal use; so, I certainly could work on that. I think we might be able to do a filesystem tree copy -- for example, track the files that get installed on the master server, then copy those to the files repository under puppet, replicate from there.
For that matter, I still think it would be useful if puppet's default install script would include a switch for "master" and "client" so that you don't get the entire distribution installed when it doesn't need to be. I'm finding that as (being a newbie) I rollout Puppet and these new releases come about, it's becoming more necessary that I find some cogent means to update puppet through the clients. Doing this manually just simply sucks and wastes time ;-) My process of rolling out ruby is pretty much the same, only I compile it locally then distribute the object/compiled code and install from there on the hosts. Thanks... -- 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.
