On Thursday 05 January 2012 07:23:33 you wrote:
> While I don't know if it's possible to negate an existing class, if what
> you're trying to do is force cfengine to unconditionally use apt-get
> rather than aptitude, then you could copy the "body package_method apt"
> promise from the stdlib, a
Hi Diego, thanks for response.
On Wednesday 04 January 2012 17:37:03 Diego Zamboni wrote:
> To unconditionally undefined a class (which is what -N does) you could
> define it as an expression that always evaluates to false:
>
> classes:
> "class_to_undefine" not => "any";
I tried that, both w
; { "foo" };
}
bundle common g {
classes:
"have_aptitude" not => "have_aptitude";
}
Thanks,
--
Michael Gliwinski
Henderson Group Information Services
9-11 Hightown Avenue, N
On Wednesday 28 Dec 2011 16:11:20 Nick Anderson wrote:
> On 12/28/2011 10:12 AM, Michael Gliwinski wrote:
> > Wouldn't that also be a problem for single cfengine "master" server (i.e.
> > cf- serverd)?
>
> Yes it would, but the nature of cfengine makes it eas
On Wednesday 28 Dec 2011 14:07:30 Nick Anderson wrote:
> On 12/28/2011 07:13 AM, Michael Gliwinski wrote:
> > Another option which I'm considering now is to let managed nodes pull
> > from VCS directly into their own masterfiles and change policy in
> > update.cf to jus
ption which I'm considering now is to let managed nodes pull from VCS
directly into their own masterfiles and change policy in update.cf to just
copy locally into inputs/ modules/ etc. after doing some local
processing/verification. Any disadvantages?
--
Michael Gliwinski
Henderson Group Infor
