[chef] Re: Re: Re: Re: Re: Re: RE: Re: Re: Re: RE: Augeas support

[Sam Darwin < >]

Andrea wrote:

" unless someone puts their money where their mouth is and starts coding an
apache2_redhat cookbook, this is moot."

You make it sounds like code must be written.   Just to be sure we are on the
same page here,  creating an apache2_redhat cookbook is very easy because it
involves REMOVING code from the existing cookbook rather than adding code.  
When you leverage the existing redhat file paths, methodologies, etc, you have
less to do on the chef side.   Not more.      The actual problem are the other
cookbooks which depend on apache, and are currently written to depend on the
"Debian-way".     In their case also it is often a process of simplification
and code removal to get them to work with Redhat, and  not the addition of
code.     So it's all backwards!  :-)      But it does still represent work 
and
attention to detail for every recipe that is affected.    No denying that 
part.