[chef] Re: Re: Re: in-house berks-api cookbook naming conflicts

[Noah Kantrowitz < >]

On Jan 6, 2015, at 3:46 PM, Torben Knerr 
<
 >
 wrote:

> There was https://tickets.opscode.com/browse/CHEF-4027 once, but it
> seems it had not been migrated to the Github issues (at least I
> couldn't find it there).
> 
> And what's so bad about referencing Git repos from a Berksfile?

You have to do it everywhere individually rather than relying on centralized 
release processes. Definitely doable on a small scale, but it can rapidly get 
unsustainable.


> It's much more explicit and transparent than overloading namespaces
> globally by pointing to a different "source" location.

Having an explicitly isolated universe of cookbooks is just as explicit, but 
it may throw some people for a loop if they are used to existing in the 
community namespace. There has been much talk of how to handle namespace 
management in the community, but little motion other than myself and a few 
others waving arms. Until something changes there, you _must_ treat the 
cookbook namespace as globally flat and thus if you want to control it you 
need to make your own bubble universe off the side.

--Noah

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail