[chef-dev] Homebrew As OS X Default Package Provider

[Joseph Anthony Pasquale Holsten < >]

We haven't needed to add macports to the omnibus-client or dev toolchain. I 
think the same is true for homebrew.

On Jul 25, 2014, at 11:26 AM, Matt Ray 
<
 >
 wrote:

> If the default package manager is Homebrew, does this mean we need to
> add it to the omnibus-client package for OSX? What about the whole OSX
> dev toolchain?
> 
> Thanks,
> Matt Ray
> Director of Partner Integration :: Chef
> 512.731.2218 :: 
> 
 
> mattray :: GitHub :: IRC :: Twitter
> 
> 
> On Thu, Jul 24, 2014 at 3:41 AM, Waldo G 
> <
 >
>  wrote:
>> Agreed.
>> 
>> 
>> On Thu, Jul 24, 2014 at 2:08 AM, Dreamcat4 
>> <
 >
>>  wrote:
>>> 
>>> Yes.
>>> 
>>> 
>>> On Thu, Jul 24, 2014 at 5:28 AM, Joseph Anthony Pasquale Holsten
>>> <
 >
>>>  wrote:
>>>> 
>>>> I may be a MacPorts package maintainer, but this is the right default. +1
>>>> 
>>>> --
>>>> http://josephholsten.com
>>>> 
>>>> On Jul 24, 2014, at 3:17, Joshua Timberman 
>>>> <
 >
>>>>  wrote:
>>>> 
>>>> Ohai Chefs!
>>>> 
>>>> I opened an issue in chef-rfc about making homebrew the default provider
>>>> for the package resource on OS X systems.
>>>> 
>>>> https://github.com/opscode/chef-rfc/issues/28
>>>> 
>>>> While I'd like to see this happen for Chef 12, I think given the
>>>> backwards compatibility issue makes that too aggressive. I'd love to hear
>>>> folks thoughts though. Please comment!
>>>> 
>>>> Thank you,
>>>> Joshua
>>> 
>>> 
>>