[chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Centralized cookbook-library repos vs distributed cookbook repos

[Adam Jacob < >]

On Wed, Apr 14, 2010 at 6:19 PM, Hedge Hog 
<
 >
 wrote:
>>
>> Is the workflow I outlined earlier not efficient enough still?
>
> Depends.
> How long do I have to wait for someone's cookbook change in the repo
> to showup in:
> /Users/adam/src/sandbox/opscode/chef-repo/cookbooks/apache2.tar.gz
>
> True,
>
> $ ./knife cookbook site vendor apache2 0.9.1
>
> is as good as
>
> $ (cd <cookbook>; git pull)
>
> I just ask:
> Is pay the price of giving up distributed cookbook development worth
> the effort saved in dependency management?
> I think that depends on the dependency mangement alternatives.
>
> My inital raction is no it is not worth it, and is worth looking into.

Right - I think we need to extend it so you can also do:

 $ ./knife cookbook site vendor apache2 HEAD

And we'll handle the case where you are willing to track the upstream
directly without a release.

Adam

-- 
Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: