Ted Zlatanov

@zzamboni should handle.

There's no way templates should be outside the sketch directory itself. But also sketches should allow customizing the template directory, in general. (I prefer to inline templates because it sidesteps...

The problem is, you're maintaining two disparate locations when you have a sketch module installed under WORKDIR/modules. For a site it makes sense; for a DC repo it doesn't. So...

The problem you're describing definitely exists. I don't want to solve it by making every sketch take a template+module path parameter, that would be tedious. I also don't want to...

Take a look at `CFEngine::dclib`, specifically the `eu` bundle: ``` # environment utilities, shortened for convenience bundle agent eu(runenv) { classes: "$(vars)" expression => "default:runenv_$(runenv)_$(vars)"; "not_$(vars)" expression => "!default:runenv_$(runenv)_$(vars)"; vars:...

I haven't been able to find a good Perl or other language module to do the full harness (create, clean up, check files). I can write my own but wanted...

You can currently do: ``` vars: "mine" slist => { "git", ... }; packages: "$(mine)" package_method => generic; # or something you can define based on the stdlib generic ```...

Right, but you'd have to always use the "generic" (or some hard-coded list) package manager. I don't know how to work around that in today's agent... we could ask for...

We'd have to supply a special generic package method, which is useless, or use the stdlib generic package method, which is not suitable for most users. Really what's needed is...

We'd be reinventing the `generic` package method and as I said, it still wouldn't cover the @atsaloli use case. I don't see how it's useful. Why not just take a...