https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7997
--- Comment #5 from Sidney Markowitz <sid...@sidney.com> --- (In reply to Henrik Krohns from comment #4) > If that's the case, sure, I guess it simplest to allow the few rules in > 01_test_rules.cf remain. Now that I think more about it, I am less sure. I didn't want to make major changes, so I left it the way it was, which is make test runs in the t directory and copies ../rules/*.cf to localrules data/01_test_rules.cf contains rules that tests can assume are defined even if make test is not run from trunk with all trunk/rules make disttest creates a subdirectory, copies MANIFEST files there (which include just a subset of trunk/rules) and runs make and make test from there clear_localrules() can be called by tests that want to make sure that they control what rules are defined. I think that clear_localrules() should clear local rules, even those in 01_test_rules.cf because those are just an arbitrary subset that were being used by tests. We can move these settings to 01_test_rules.pre because they are settings, not rules. What do you think? clear_report_template report _SUMMARY_ clear_headers add_header spam Flag _YESNOCAPS_ add_header all Level _STARS(*)_ add_header all Status "_YESNO_, score=_SCORE_ required=_REQD_ tests=_TESTS_ autolearn=_AUTOLEARN_ version=_VERSION_" ifplugin Mail::SpamAssassin::Plugin::DCC use_dcc 0 endif ifplugin Mail::SpamAssassin::Plugin::Razor2 use_razor2 0 endif ifplugin Mail::SpamAssassin::Plugin::Pyzor use_pyzor 0 endif -- You are receiving this mail because: You are the assignee for the bug.
