Really? Huh... that's weird... I'd file a bug report with an example, if I
were you...
-Dan
On Jul 15, 2011, at 2:56 AM, no-re...@cfengine.com wrote:
> Forum: CFEngine Help
> Subject: Re: ${this.promiser} in comments
> Author: svenXY
> Link to topic: https://cfeng
On Fri, Jul 15, 2011 at 09:44:08AM +0200, Mark Burgess wrote:
> On 07/15/2011 09:31 AM, Mikhail Gusarov wrote:
> > Seems to be a bug. Please open a bug in our bugtracker.
> [...] there is no difference in the way that () and {} are handled.
> Logically, there should be full symmetry between these c
On 07/15/2011 09:31 AM, Mikhail Gusarov wrote:
> On 15.07.2011 08:56, no-re...@cfengine.com wrote:
>
>> right, thanks for your thoughts on this, but apparently $(this.promiser) is
>> expanded all right whereas ${this.promiser} is not.
> Seems to be a bug. Please open a bug in our bugtracker.
>
>
On 15.07.2011 08:56, no-re...@cfengine.com wrote:
> right, thanks for your thoughts on this, but apparently $(this.promiser) is
> expanded all right whereas ${this.promiser} is not.
Seems to be a bug. Please open a bug in our bugtracker.
--
Mikhail Gusarov
Forum: CFEngine Help
Subject: Re: ${this.promiser} in comments
Author: svenXY
Link to topic: https://cfengine.com/forum/read.php?3,22798,22806#msg-22806
Hi Dan,
right, thanks for your thoughts on this, but apparently $(this.promiser) is
expanded all right whereas ${this.promiser} is not.
I
Sven-
This was reported as a bug on 2010/02/26 and reported as partially resolved
2010/03/19 in https://cfengine.com/bugtracker/view.php?id=58 - here is the
resolution notice: "This can only be partially fixed. The reason is that the
precise knowledge of this.promiser comes too late to use in t
Hi,
I just found out that ${this.promiser}
is not resolved in comments whereas $(this.promiser) is
files:
any::
"${tmpdirs}"
handle =>
"fix_tmp_dirs",
comment
=> "Fix permissions of tmpdir $(this.promiser)",
perms =>
m("1777");
"${tmpdirs}"
hand
