On Tue, 22 May 2012 15:11:23 -0500 Nick Anderson <n...@cmdln.org> wrote:
NA> So in general are you preferring prefix to passing an array name with NA> new sketches? And also are you preferring a single usebundle call for NA> each different configuration? Yes, and yes. It makes passing data between JSON, Perl, and CFEngine much simpler. I expect that if and when we get true bundle metadata, this mechanism will change, so don't worry too much about it :) NA> I try to error on the side of defaults. With regard to file NA> distribution the default bootstrap policy wont copy .template files NA> iirc only .cf .dat and .txt files are copied by default. ... NA> I am curious as to what you and others think the accepted norm NA> should be for the design center. I assume that if it's in the manifest, it should be copied. Sketches should Just Work, so the less you have to remember and copy, the easier they will be. In the context of your custom policies it may not make sense to copy everything, but a sketch is much more coherent and single-use. NA> On a side note I suggest another rename, perhaps to vcs_freshenup or NA> vcs_cleanup. NA> clone terminology doesn't really apply to svn well. freshenup or NA> cleanup is pretty generic. Hey, it's your sketch name ;) How about vcs_mirror? That's pretty clear and the term is not used by Git or Subversion. If you agree I'll make the change on my side. NA> # TODO: provide some way to selectivly contain the executing user Yeah, good point. That should be optional and default to null, meaning "use the current UID." WDYT? Ted _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
