[chef] Re: Re: Re: chef-client cookbook and log rotation

[Joshua Timberman < >]

To clarify on something here (had it in a draft, got lost along the way):


On 12/18/12 7:17 PM, "Joshua Timberman" 
<
 >
 wrote:

>One thing we prefer to do is keep individual components free of
>interdependence on other cookbooks, because it is less surprising. We
>don't always do this, and we can't always do this, each cookbook is an
>individual project with its own considerations here.
>
>That said, we're not entirely consistent, and working to improve that.

By less surprising, I mean "it works like you'd expect [for the most
common use case(s)]."

This is hard to do consistently, because some users don't expect another
cookbook to come along as a dependency. For example, "why do I have this
'windows' cookbook, I'm using RHEL." Answer, because some other cookbook
depended on it, even though it might be a niche use.

Similarly, "why doesn't the cookbook depend on 'build-essential'? It has a
source compiling recipe." Likewise, that isn't a common use case and
perhaps the default recipe installs a package rather than compiling from
source, and generally people who want to compile many things from source
would have 'build-essential' elsewhere in their run list (like the base
role).

So that's more what I mean about considerations and consistency. We're
working to improve this in cookbooks, and we have tickets for Chef to use
the various parts of cookbook metadata more meaningfully (like
recommends/suggests).

-- 
Opscode, Inc
Joshua Timberman, Technical Community Manager
IRC, Skype, Twitter, Github: jtimberman