Marco Marongiu <brontoli...@gmail.com> wrote: >> Where did this come from? We already handle this using classes. Why >> add another method to muddy the waters? Changing a feature's main >> purpose from documentation to functional leaves me dumbfounded. >[...] >> We can already reorder promises using classes. What purpose is >> served by adding another method? Classes were the sole construct for >> decision making. No longer. Consider un-ringing this bell before >> 3.4.0 goes GA. > >Neil, I think you succeeded in expressing my concerns. > >When this feature was announced, I said that it was "puppetish". I was >not sure how it could fit into cfengine's design, but I couldn't see >exactly where things didn't hang together. You clarified that, at least >in one aspect. Thanks. > >My first concern remains, however. We already have ways to reorder >promises that are consistent with cfengine's design. We don't need to >mock puppet. > >Ciao >-- bronto >_______________________________________________ >Help-cfengine mailing list >Help-cfengine@cfengine.org >https://cfengine.org/mailman/listinfo/help-cfengine
I see it as a shortcut when order is needed and there is real dependence this will make the policy more concise and easy to read. -- Sent from Kaiten Mail for Android. Please excuse my brevity. _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
