Hi Jeremiah,thanks for writing this up! I was basically considering the same approach, i.e. moving my cookbooks outside of the chef-repo so I can track them in their individual git repos without having nested git repos in my chef-repo. I also came across librarian and had something similar in my head, but I didn't put it into practice yet...Without ever having tried it out, how does librarian handle dependency conflicts? Consider the following cookbook dependencies:foo v1.0 -> baz v1.0bar v1.0 -> baz 2.0I believe chef-server can host multiple versions of the same cookbook, but how does librarian handle this situation? Will it add the version number to the cookbooks it creates inside chef-repo/cookbooks?Another question that maybe someone from OpsCode can answer: will `knife cookbook site install` be deprecated or remain as-is now that the OpsCode cookbooks are organized in individual git repos? As Jeremiah already mentioned in his writeup there seems to be an impedance mismatch as you "lose" the source / origin of the cookbooks with the `knife cookbook site install` approach.
Cheers,TorbenOn Sun, Apr 22, 2012 at 2:25 PM, Jeremiah Snapp < " target="_blank"> > wrote:
It occurs to me that I may be confusing things by using the name site-cookbooks for the directory that actually only holds rare, infrastructure specific cookbooks rather than vendor cookbooks. Would you suggest I use a different name? Any ideas?
I will update my write up soon to try to clear these things up. It might be a couple of days from now though since my wife is five days over due with our second son. :)
Archive powered by MHonArc 2.6.16.