[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: module macros are expanded too late - was Determining Solarispatch r
Martin, Jason H
RE: module macros are expanded too late - was Determining Solarispatch revisions
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.
> -----Original Message-----
> 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."
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
Help-cfengine mailing list
- RE: module macros are expanded too late - was Determining Solarispatch revisions,
Martin, Jason H <=