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

[Daniel DeLeo < >]

On Thursday, October 3, 2013 at 12:14 PM, Thom May wrote:

On Thu, Oct 3, 2013 at 11:14 AM, Daniel DeLeo < " target="_blank"> > wrote:

On Thursday, October 3, 2013 at 11:10 AM, Blake Irvin wrote:

On Thu, Oct 3, 2013 at 1:09 AM, Sean OMeara < " target="_blank"> > wrote:

Why can't we just switch to client-side dependency solving instead? (ala berks)

Yes please.

I think this will happen on a Chef 12-ish timescale. There's a lot of work required, and it will have pretty big impacts on workflow, which I think will be for the best.

Is there a draft of this, Dan? Or is it a whiteboard scribble right now? :)

It's more at the level of whiteboard scribble. There are a few relevant design proposals I've floated to people as gists, such as this one:

https://gist.github.com/danielsdeleo/7c55ebe39639928134df

But some bits of that proposal have been obsoleted by better ideas/experience/learning.

-- 

Daniel DeLeo