[chef] Re: Re: Re: Contributing to Cookbooks (was chef & hoptoad)

[Alex Soto < >]

I think the knife cookbook vendor command takes care of the need to have your 
own jm_cookbook.  Just vendor the cookbook, make your tweaks.  If you wish to 
update from upstream, you pull use the vendor command again and fix any merge 
conflicts.

Take with a grain of salt.  I've vendored but haven't needed to pull in 
upstream changes yet, but I'm assuming if my changes are minor, merges should 
be fairly painless.

Alex

On Jul 15, 2010, at 5:07 PM, John Merrells wrote:

> 
> On Jul 15, 2010, at 3:31 PM, Alex Soto wrote:
> 
>> 
>> First I mainly spend my time with chef developing cookbooks, so how would 
>> I 'contribute' a cookbook while not incurring a lot of overhead ?  For 
>> example, I create a cookbook that I haven't seen in the wild, I'd like to 
>> publish it for others to use and enhance, but since it's in my private 
>> repo, how would I do that?
> 
> Thanks to Josh's informative emails, I've been pondering on this in the 
> background most of the afternoon.
> 
> Looking at my site-cookbooks I notice that there's a pattern developing. I 
> tend to create subclass cookbooks.
> So, for example I'll create site-cookbooks/jm_memcached, which includes 
> cookbooks/memcached, and then
> adds my own twiddles. I think this addresses the public vs private problem.
> 
> Adding my initials to the name is kinda icky, but if this is a common 
> pattern then Chef/Knife could codify 
> it with some namespace support, or cookbook inheritance, or something.
> 
> John
> 
> -- 
> John Merrells
> http://johnmerrells.com
> +1.415.244.5808
> 
> 
> 
> 
> 
>