heavywater/pennyworth — Issue #17: Extract customized cookbooks for simpler project remixing?
Author: patcon
Created: 2011-12-12 15:57:29+00:00
State: open

Hey man,

I don't suppose there's any way you could be convinced to pull any non-conventional (or customized) cookbooks into separate chef-COOKBOOKNAME repos, or something comparable? I'm trying to work within [these conventions](https://github.com/FLOSolutions/fga-chef-repo) (still in flux, to be fair), and right now we're hosting our own versions of your cookbooks repos, which is going to add to overhead.

https://github.com/patcon/pennyworth/tree/heavywater-5_librarian-chef
https://github.com/patcon/chef-jenkins/tree/pennyworth
https://github.com/patcon/chef-reprepro/tree/pennyworth
https://github.com/patcon/chef-pennyworth

Seems having them separate would also make it simpler for other people to use your cookbooks individually and hack on them, without having to pull them out and lose history and metadata.

Might've mentioned it before, but I just extracted the history (and added it to opscode's history when relevant) using this method:
http://psionides.eu/2010/02/04/sharing-code-between-projects-with-git-subtree/