On Fri, 6 Jul 2012 16:21:11 +0200 (CEST) neilhwatson wrote:
n> Doesn't [namespacing] just push the concern to a different layer? Now my
bundles can be anything but, I have to worry if my namespace is unique.
Most of Computer Science and Engineering deals with pushing things to a
different layer :)
It would be nice if the namespace could be set to "auto" from the
filename, the equivalent of canonicalize("$(this.promise_filename)") but
in the namespace control. Then you're fairly guaranteed there will be
no conflict within the local installation.
In the CFEngine context, it's reasonable to assume that no one else will
take the "neilhwatson_*" namespaces. So you could use that for your own
work. But the intent of the feature is to control variable and class
scope within a closed ecosystem like the Design Center with local
policies on top, not to provide absolute namespacing.
If you want to make sure you don't conflict with the Design Center
namespaces, for instance, you'd register your namespace with the Design
Center maintainers, who would then ensure it's not used by anyone. I
think this is a reasonable approach and volunteer to maintain the
namespace registry, with the understanding that it's entirely voluntary
to use it and it's as dependable as the policy writers' intent to
respect it. It will live in $(DESIGN_CENTER)/sketches/namespaces and I
just pushed the first cut, with
cfdc design-cen...@cfengine.com
as the only line.
Ted
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine
