On Oct 25, 1:25 pm, Todd Zullinger <t...@pobox.com> wrote: > Maciej Skrzetuski wrote: > > Do you mean hosting your own yum repository in your own network? > > That is not a bad idea but it would be easier to just copy the files > > over to the puppets and then just rpm -ihv <package>, wouldn't it? > > No, it wouldn't be. You lose yum's ability to install depndencies for > one.
Also, it's messy and non-trivial to persuade Puppet that it only needs to copy the RPMs if the package isn't already installed. You might partially work around that by placing them in a network-accessible location (e.g. on an NFS share) to avoid the copying, but yum inherently downloads only the RPMs it needs. It really is very easy to set up a yum repository. It's also easy to use Puppet to tell your clients about it (see the Yumrepo resource). You should hack together a poor man's alternative only if there is a surpassingly strong barrier to using yum. John -- 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.
