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

[Martin, Jason H]

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: 
> help-cfengine-bounces+jason.h.martin=cingular.com@gnu.org 
> [mailto:help-cfengine-bounces+jason.h.martin=cingular.com@gnu.
> org] On Behalf Of Ed Brown
> Sent: Friday, September 23, 2005 10:25 AM
> To: rader@ginseng.hep.wisc.edu
> Cc: Help-cfengine@gnu.org
> Subject: Re: module macros are expanded too late - was 
> Determining Solarispatch revisions
> 
> 
> On Fri, 2005-09-23 at 06:20, rader@ginseng.hep.wisc.edu 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
Help-cfengine@gnu.org
http://lists.gnu.org/mailman/listinfo/help-cfengine