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

[Seth Falcon < >]

 writes:
> I like this.  It's better than 'suggests' just being a no-op.  An
> alternative may be to enable case statements in metadata.rb.  The
> individual depends could then properly be resolved based on platform
> or recipe usage.  The client can then filter based on the case in the
> cookbook's metadata, and only download those cookbooks it really
> needs.
>
> This would be a further step towards making metadata actually useful.
> It remains to be seen which is more easily implemented/accepted.

One small note on making any of the cookbook version metadata fields
"active" rather than no-ops. Presently, there are many cookbooks that
have values in these fields. If the server or client starts to use these
fields, we'll have many cookbooks in the wild with invalid values. So as
an implementation detail, we may want to consider a new name.

+ seth


-- 
Seth Falcon | Development Lead | Opscode | @sfalcon

Attachment: pgpOERdmY3sn5.pgp
Description: PGP signature