[chef] Re: Versioning forked cookbooks


Chronological Thread 
  • From: Ranjib Dey < >
  • To: " " < >
  • Subject: [chef] Re: Versioning forked cookbooks
  • Date: Fri, 8 Aug 2014 12:34:06 -0700

generally, we use librarian (or berks) to manage the community cookbooks, and point it to our forked repo till the patch is being merged and revert back to the upstream version when its available. This same workflow as any other rubygem + bundler
regards
ranjib


On Fri, Aug 8, 2014 at 12:18 PM, Andrew Brown < " target="_blank"> > wrote:
Ohai Chefs,

I have a question about how to version forked community cookbooks.  In our environment, we require a patch to the cron community cookbook, since it doesn’t exactly meet our needs.  Since a patch has also been submitted to upstream, eventually the community version will increase its version, possibly conflicting with ours.  As well, at some point in the future, we would like to switch back to the community version once the patch is accepted.

Given this background, how would you suggest to version the cron cookbook, as well as cookbooks that include it as a dependency?

Thanks!
Andrew




Archive powered by MHonArc 2.6.16.

§