help-cfengine
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: module macros are expanded too late - was Determining Solarispatch r


From: Martin, Jason H
Subject: RE: module macros are expanded too late - was Determining Solarispatch revisions
Date: Fri, 23 Sep 2005 10:41:44 -0700

I'm using prepmodule to define classes and variables, which is necessary
so CFE doesn't prune actions based on the classes defined by the module.


-Jason Martin

> -----Original Message-----
> From: 
> address@hidden 
> [mailto:address@hidden
> org] On Behalf Of Ed Brown
> Sent: Friday, September 23, 2005 10:25 AM
> To: address@hidden
> Cc: address@hidden
> Subject: Re: module macros are expanded too late - was 
> Determining Solarispatch revisions
> 
> 
> On Fri, 2005-09-23 at 06:20, address@hidden wrote:
> 
> >    sl3 = ( PrepModule(HasSL,"noargs") )
> 
> By the way, for PrepModule, the class is "True if the named 
> module exists and can be executed." 
> (http://www.cfengine.org/docs/cfengine-Reference.html#index-Pr
epModule-3)
This in itself seems kind of useless.  The documentation doesn't explain
if the output (+ClassName) is also used as it is with regular modules. 
My 'module' was just a shell script with /bin/true.

Anybody using PrepModule to define classes/variables inside the module? 
When is it useful to define a class just based on a module existing and
being executable?

-Ed  



_______________________________________________
Help-cfengine mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/help-cfengine




reply via email to

[Prev in Thread] Current Thread [Next in Thread]