[chef] Re: Re: cookbook version

[Gilles Devaux < >]

Is there a document on how cookbook merges are handled with versions?

I migrated to chef 0.9 recently and with 0.8 I relied on cookbook
merges between /cookbooks and /site-cookbooks. I used it to still use
nginx::source but with [:nginx][:configure_flags] <<
"--with-http_stub_status_module" by default. My site-cookbooks/nginx
just contained an attribute file.

Turns out that if I version my cookbooks with the same version as the
one in ./cookbooks but this make things difficult to maintain when
updating the base cookbooks.

Is there a way to handle this nicely or should I completely revise my
strategy in order to use the common opscode/chef repo and modify the
minimum to suite my needs?

Thanks

--Gilles

On Wed, Aug 4, 2010 at 4:05 AM, Thom May 
<
 >
 wrote:
> On Wed, Aug 4, 2010 at 11:02,  
> <
 >
>  wrote:
>> hi
>>
>> can someone explain me how cookbook version work ? does it mean that I can 
>> have
>> multi version of one cookbook and specify in run_list which version will be
>> used ?
>>
>
> That's how it will work, yes. The code is scheduled to land in 0.10
> AIUI; you can have and store multiple versions of cookbooks right now,
> but there's no way to select which one to use - you'll always get the
> latest one.
> -t
>