I tend to agree with you, Christopher, that the first priority is to make clear the *intentions* behind the configuration -- human understanding (knowledge management) is often sacrificed for efficiency. We should strike a balance.
Neil's solution is technically elegant, but by separating data and method so completely the two seem now disconnected -- and their meaning becomes obscured. M Christoph Maser wrote: > Am Mittwoch, den 09.12.2009, 19:30 +0100 schrieb nwat...@symcor.com: >> I've made good progress is producing reusable policies with CF3. Consider >> a security policy that checks the permissions of a motley group of files. >> At first one might consider setting a a list or two and going from there. > > > Nice cool work, but why all these shortcuts? Especially if you talk > about reusability you should optmize your code for readability, not for > number of bytest ;) > > Chris > > > financial.com AG > > Munich head office/Hauptsitz München: Maria-Probst-Str. 19 | 80939 München | > Germany > Frankfurt branch office/Niederlassung Frankfurt: Messeturm | > Friedrich-Ebert-Anlage 49 | 60327 Frankfurt | Germany > Management board/Vorstand: Dr. Steffen Boehnert | Dr. Alexis Eisenhofer | Dr. > Yann Samson | Matthias Wiederwach > Supervisory board/Aufsichtsrat: Dr. Dr. Ernst zur Linden > (chairman/Vorsitzender) > Register court/Handelsregister: Munich – HRB 128 972 | Sales tax ID > number/St.Nr.: DE205 370 553 > _______________________________________________ > Help-cfengine mailing list > Help-cfengine@cfengine.org > https://cfengine.org/mailman/listinfo/help-cfengine -- Mark Burgess ------------------------------------------------- Professor of Network and System Administration Oslo University College, Norway Personal Web: http://www.iu.hio.no/~mark Office Telf : +47 22453272 ------------------------------------------------- _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
