Jo Rhett wrote:
Yesterday Eric mentioned:FWIW, the other PackageList and PackageCheck functions output this message at Verbose() level, might want to keep it consistent.Yes, we should go through all of these and make them consistent. I'll do that next week (this week is already a write-off)
Yes, please.
Verbose: output should make clear to the cfengine administrator what their configuration syntax resolves to.Debug: output should make clear to the cfengine hacker what their code is really doing on the cfengine's administrator's system, when he reports a bug.
In short, any query to cfengine-help should include Verbose output, and any query to cfengine-bug should include Debug output.Does this make any sense?
Yes, and it's nice and clear--a good thing. Two comments/questions:1) Will --debug include the same information as reported by --verbose? Is there any information in --verbose that is not reported in --debug?
2) I've found that when troubleshooting my rules (usually of the "why didn't this run?" type), the output from --verbose is insufficient. Usually because I'm trying figure out why a class or variable has been set (or not). If there's a clean way of reporting these two things in --verbose mode, that would be wonderful. (maybe a -vv sort of option?)
-- Jesse Becker NHGRI Linux support (Digicon Contractor)
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Bug-cfengine mailing list [email protected] https://cfengine.org/mailman/listinfo/bug-cfengine
