On Thu, Sep 20, 2012 at 9:28 AM, Philip Brown <[email protected]> wrote: > On Thu, Sep 20, 2012 at 9:03 AM, Andy Parker <[email protected]> wrote: >> >> Yeah, even when a provider is specified it'll check the others to see >> if they would work. I'm not certain why that is done, but may not be >> needed. However, I dont' think it is causing the problem. >> > > Erm.. we seem to be having a communications breakdown. > I'm saying, that IS the problem :) > Particularly on a system like solaris, where it has multiple possible > package providers, so the other providers will note that they CAN > work, and maybe override stuff. > Not good, when I've explicitly defined the provider I want puppet to use.
Puppet will use the package provider you specified. This is a trivial example where users can specify package provider => gem (shipped with puppet) or provider => pe_gem (provided by the module): https://github.com/puppetlabs/puppetlabs-pe_gem Thanks, Nan -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
