[chef-dev] Re: Re: Re: dependency spaghetti

[Lamont Granquist < >]

Shouldn't berkshelf make it easier to fork a community cookbook and 
modify the depends, and then merge upstream periodically when you need 
to and point your berkshelf at your local copy?  It certainly works 
better than the previous knife cookbook site stuff, and merge conflicts 
over the depends should be pretty easy to deal with...

On 10/2/13 7:05 PM, Noah Kantrowitz wrote:
> The problem is as we move the community to Berkshelf and tools like it (which 
> is totally the right direction) you can't just edit the upstream cookbooks 
> since you never see them directly. Optional dependencies would help, but the 
> user experience if you are missing an optional cookbook is definitely not 
> great and we'll need some improvements there. The real dream is some kind of 
> declarative way to state when a dependency is needed, but so far I've not 
> seen any proposed way to do that which doesn't veer off into crazytown.
>
> --Noah