[chef] Attribute ordering in nested Roles

[Jonathan Matthews < >]

Hey all -

Is it intended (chef-client & -server 0.9.8 via RPMs) for a Role's
defaults and overrides to be applied /before/ those of any Roles that
it itself includes in its run_list?

I'm seeing this behaviour whilst trying to dictate which httpd MPM I'd
like used.  To my mind, it makes sense for a an (arbitrary) "App_XYZ"
Role to include an "httpd_server" Role (rather than merely apply them
in order, directly on the Node I'm interested in), but it requires
MPM:prefork.  The fact that App_XYZ's Attributes seem to be applied
before httpd_server's means I can't pull in everything that
httpd_server provides and then selectively override the MPM setting
from httpd_server's default of MPM:worker.

Would it not be more sensible for the *including* Role's defaults to
be applied first, then the defaults/overrides from the Roles it
includes, and finally the overrides from the including Role?

If I've missed something fundamental or a previous flamefest on this
issue, please do point me towards it and - if possible - an
explanation of how I should better achieve what I've described!

Cheers,
Jonathan
-- 
Jonathan Matthews
London, UK
http://www.jpluscplusm.com/contact.html