On Sep 11, 2007, at 10:41 AM, Daniel Dehennin wrote: > Using list for package make version check quite useless. It permit to > express a sort of dependencies between packages without adding number > of classes.
But without being able to express a version I'm not sure I see how this could be useful. Much better to use define= to set that up (and easier to read) > I don't say it relevant, I'm quite new to cfengine and I'm not sure to > catch its whole philosophy. I'll not ask to add something which seems > useless for everybody (maybe including me ;-)). Perhaps not useless, I'm just having trouble seeing the value. In my experience it is always best to find a realworld scenario that supports your goal, and try to write a configuration file that supports it. It tends to clarify the issues in your mind very quickly. Attempts to armchair this would having a realworld scenario to discuss don't seem to end well, even when I try to do them ;-) That's why I like having a real-world, clearly defined need. > I was thinking about this to permit to define a class when a package > is installed. For now, define is triggered if the package is already > installed, not when the action=install is done. Right. That will be simple enough in C. I simply haven't done it because as it turns out it hasn't been a limitation in my environment ;-) Once someone bugs me about a real-world need I'll write it out. It just requires some more data structures to track variables with the package to install. -- Jo Rhett senior geek Silicon Valley Colocation Support Phone: 408-400-0550 _______________________________________________ Bug-cfengine mailing list [email protected] https://cfengine.org/mailman/listinfo/bug-cfengine
