On Thursday, June 9, 2011 at 9:07 AM, Sergio Rubio wrote:
> > Feel free to hop on to #chef-hacking on freenode.net (http://freenode.net) (http://freenode.net) if you have development questions, or you can mail the chef-dev list as well.
> On Thu, Jun 9, 2011 at 5:36 PM, Daniel DeLeo < "> (mailto: "> )> wrote:
> >
> > On Thursday, June 9, 2011 at 8:32 AM, Sergio Rubio wrote:
> >
> > > If you guys feel like both approaches are valid, I can add a patch to the Chef RPM to alleviate some of the pain the CentOS users are dealing with.
> > >
> > > Rgds.
> > Yeah, that would be great. I'm in favor of switching popen4 to shell_out if you can since the API is cleaner and it has built-in support for nice error messages when a command fails as well as live updating of output to a tty in some conditions.
> >
>It would be best if you could create a ticket on our JIRA, tickets.opscode.com Let me know the ticket number and I'll fast track it for this release since this is a blocking issue for many of you.
> Alright. I've modified the patch to use shell_out:
>
> https://gist.github.com/1016667
>
> And the full yum.rb file in case anyone wants to test it:
>
> https://gist.github.com/1017053
>
> (replaces /usr/lib/ruby/gems/1.8/gems/chef-0.10.0/lib/chef/provider/package/yum.rb)
>
> My plan is to do some more testing and If everything goes well, I'll push an updated RPM soon after that.
>
> I've seen that there are a lot of changes coming to the yum provider in the next release, so I guess submitting a pull request is not necessary, right?
>
> Rgds.
>
--
Dan DeLeo
>
> > --
> > Dan DeLeo
> > > > --
> > > > Dan DeLeo
Archive powered by MHonArc 2.6.16.