Yeah, if you are maintaining a public repository which will never
get pushed upstream to opscode it makes sense to use a bare branch.
In the sense that it makes no sense to track upstream changes for a
community cookbook which has no shared development history with
opscode/master However, if you are pushing changes to an official opscode cookbook, you have to keep that development history for a clean merge upstream. Eric G. Wolfe Senior Linux Administrator, IT Infrastructure Systems -------------------------------------- Marshall University Computing Services Drinko Library 428-K One John Marshall Dr. Huntington, WV 25755 Phone: 304.696.3428 Email: "> Admiration, n.: Our polite recognition of another's resemblance to ourselves. -- Ambrose Bierce, "The Devil's Dictionary" On 12/05/2011 03:12 AM, Bryan Berry wrote: " type="cite"> I have rewritten the java cookbook to use the java_cpr lwrp (Crappy Package Resource). This LWRP provides an easy way to manage java applications. It is "crappy" because it is very simple and barely deserves being called a package resource. Essentially, you provide the java_cpr with the URL to a tarball and |
Archive powered by MHonArc 2.6.16.