Totally agree with both of you, and we had planned on setting up our custom repo in the near future. This was really just going to be an interim solution for us, and more generally an optional solution for adhoc/masterless puppet deployments. While I think having a custom repo is the elegant and scalable solution, I still think there are scenarios where it doesn't make sense to spin up a yum server (or deploy one on the localhost) just so I can install an rpm that's sitting in my home directory. Given that yum supports the ability to install from local, I'd still call this a puppet bug :)
Anyway, thanks for the input, sounds like the yum repo just became a higher priority. P On Monday, June 10, 2013 7:18:05 AM UTC-7, jcbollinger wrote: > > > > On Saturday, June 8, 2013 12:56:22 PM UTC-5, Ygor wrote: >> >> If the local install is not working, then just do it from your custom, >> local repo >> >> > > +1 for setting up a local repository. This is FAR better than slinging > around RPM files (semi-)manually or serving them directly from some shared > filesystem. > > > John > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
