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

[Cassiano Leal < >]

> -----Original message-----
> > From:Joshua Timberman <
>  
>  ">
>  >
> > 
> > By all means, don't use the community cookbook if it doesn't fit your preference, use case, supported platforms or standards.
>
> Totally understood. Unfortunately, when it comes to such a basic cookbook as Apache, that means foregoing a very large share of the benefit of Chef - too many community cookbooks depend on it.

I have been thinking about this problem for a while now. I believe that what Chef needs here is something similar to Virtual Packages on the Debian packaging system.

Basically, abstract notions of a functionality, whose actual implementation is delegated to one or more packages (or in Chef's case, cookbooks).

This way, there could be a "virtual cookbook" apache, that's implemented by whatever apache cookbook I want to use -- be it opscode's, my own homebrewed, or someone else's like something I found on github and that serves my needs.

I'm not sure about the feasibility of such approach, but I'd like to see something along these lines implemented.

Thoughts?

- cassiano