[chef] Splitting Chef::Client and Chef::Server into their own cookbooks

[Jon Wood < >]

Hi there,

I've just started building my first Chef repository that will be
running from the Opscode platform, and in doing so have realised just
how many cookbooks the Chef cookbook brings along with it as
dependencies.

While that's not the end of the world, it is a bit frustrating to have
things like couchdb and erlang in my cookbooks directory, when I know
I'm unlikely to need to them, and wonder what people feel about
splitting the client and server components into separate cookbooks.

My proposal is to have anything client related in chef-client, server
in chef-server, and keep an all encompassing chef cookbook which
depends on both, and just includes the appropriates recipes for
compatibility, but I'm open to suggestions, including "stop worrying
about your messy repository and get on with life".

Cheers,
-- 
Jon Wood
Blank Pad Development

07827 888143