why chef-rvm and not rvm? about rvm

[fnichol]

There were a couple of reasons that the repo ended up as chef-rvm. The most basic was that I needed a way to distinguish the Chef cookbook from the RVM project proper :) There also seems to be an emerging pattern where cookbook-as-a-git-repo codebase names are being prepended with chef- or appended with -cookbook. And finally, the knife-github-cookbooks knife plugin explicitly supported this convention.

The main issue is that the cookbook won't work out of the box unless it's renamed from chef-rvm to rvm due to some dynamic module/class construction. Does that help shed some light (thanks for the question BTW)?

[mlitwin-rpx]

Yes it does, thanks. We are with RightScale so we don't use knife. This makes forking a bit of an issue, but knife is really how things should be done to deal with just this sort of thing. We are just behind the times.

On Dec 10, 2011, at 8:16 PM, Fletcher Nichol wrote:

There were a couple of reasons that the repo ended up as chef-rvm. The most basic was that I needed a way to distinguish the Chef cookbook from the RVM project proper :) There also seems to be an emerging pattern where cookbook-as-a-git-repo codebase names are being prepended with chef- or appended with -cookbook. And finally, the knife-github-cookbooks knife plugin explicitly supported this convention.

The main issue is that the cookbook won't work out of the box unless it's renamed from chef-rvm to rvm due to some dynamic module/class construction. Does that help shed some light (thanks for the question BTW)?

---

Reply to this email directly or view it on GitHub:
#59 (comment)

[pearcec]

Use librarian, and it is a non issue.

[fnichol]

@pearcec agreed, the librarian gem is a great way to manage your cookbooks/ directory. Kudos to @yfeldblum for such a great solution :)

[fnichol]

I'm going to close this out for now. If anyone has further concerns or questions, just re-open!

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.