Le 5123 Septembre 1993, Jo Rhett a tapoté: > I agree that this might be a worthy goal, but I am looking at the code
[...] > Yeah, the more I think about it the more I think that this syntax has > such very limited use (ie *never* for any standard packages -- only > for locally built packages where versions can be kept in sync?) that > I can't figure out why it has value to you enough to spend time > writing the patch. Using list for package make version check quite useless. It permit to express a sort of dependencies between packages without adding number of classes. 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 ;-)). > *shrug* You could do it and submit it to Mark to see if he wants to > include it. I'm not sure that he would see value in putting pkmgr- > specific code into cfengine. (I mean lots of it, rather than just a > routine which invokes the pkgmgr) I'll not do it, it's C++ and I'm not the kind of man who can use C++ in C ;-) 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. I thougt that we can (for some package manager) change this. I'll continue to experiment with cfengine, and keep you informed about my "ideas". > I've CCed bug-cfengine which appears to be the dev list in practice. Ok. Regards. -- Daniel Dehennin Récupérer ma clef GPG: gpg --keyserver pgp.mit.edu --recv-keys 0x6A2540D1 _______________________________________________ Bug-cfengine mailing list [email protected] https://cfengine.org/mailman/listinfo/bug-cfengine
