[chef-dev] Re: Re: CHEF-2988 allowed_recipes, restricted_recipes, and override_recipes

[Peter Donald < >]

Hi,

On Thu, Mar 29, 2012 at 6:49 AM, Bryan McLellan 
<
 >
 wrote:
> Again, as features, we're not convinced that the value of allowed and
> restricted cookbooks are greater than what you can do with an override
> runlist.

I see them as two completely different concerns. Restricting cookbooks
allows you to control the expansion of dependencies to remove features
that are never used in your infrastructure. Almost all module systems
that allow you declare dependencies allow you the ability to prune the
dependency tree in some fashion.

* In most maven projects you will see people explicitly overriding
dependencies to try and stop "downloading of the internet" and there
is a difference between scopes
* In OSGi there is all sorts of tricks around dependencies and which
are optional/required etc
* In RubyGems you distinguisd between development and non-development
scope but also end up generating different specs based on platform
(See jruby guff in
https://github.com/apache/buildr/blob/trunk/buildr.gemspec)
etc


-- 
Cheers,

Peter Donald