[Top][All Lists]

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

Re: editfiles template; multiple edits; setting a class on update

From: Tim Nelson
Subject: Re: editfiles template; multiple edits; setting a class on update
Date: Wed, 25 Jan 2006 14:30:06 +1100 (EST)

On Tue, 17 Jan 2006, Brendan Strejcek wrote:

Russell Adams wrote:

I think everyone ought to learn m4. It simplifies things immensely.


I'm not sure I agree. Everyone interested in understanding the
traditional Unix tool set should learn m4, because it is ubiquitous.
But it has some limitations that are pretty nasty, such as escaping
characters and quotation (which do not behave in an intuitive way).

In the context of system management, everybody should think about
templating and preprocessing, but I can't really recommend m4 as a
templating tool. I do still use m4 in my cfengine config, but it feels
brittle, and I doubt anyone else at my site really understands it.
There are several other templating engines out there, such as Perl's
Text::Template. I have actually found that php is one of the most
flexible and maintainable general preprocessors.

...and if you want a Text::Template setup that's got some built-in cfengine stuff, try cfengine-masterconf, and click on cfengine-masterconf.


Help-cfengine mailing list

Kind Regards,
Tim Nelson
Server Administrator
P: 03 9934 0888
F: 03 9934 0899
E: address@hidden
WebAlive Technologies
Level 1, Innovation Building
Digital Harbour
1010 La Trobe Street
Docklands Melbourne VIC 3008

This email (including all attachments) is intended solely for the named 
addressee. It is confidential and may contain legally privileged information. If
you receive it in error, please let us know by reply email, delete it from your 
system and destroy any copies. This email is also subject to copyright. No
part of it should be reproduced, adapted or transmitted without the written 
consent of the copyright owner.

Emails may be interfered with, may contain computer viruses or other defects 
and may not be successfully replicated on other systems. We give no
warranties in relation to these matters. If you have any doubts about the 
authenticity of an email purportedly sent by us, please contact us immediately.

reply via email to

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