You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by jm...@apache.org on 2006/09/02 23:00:09 UTC
svn commit: r439651 - /spamassassin/trunk/build/automc/run_preflight
Author: jm
Date: Sat Sep 2 14:00:09 2006
New Revision: 439651
URL: http://svn.apache.org/viewvc?rev=439651&view=rev
Log:
I keep wondering why rules aren't appearing in the preflight mass-checks; might as well run the lot
Modified:
spamassassin/trunk/build/automc/run_preflight
Modified: spamassassin/trunk/build/automc/run_preflight
URL: http://svn.apache.org/viewvc/spamassassin/trunk/build/automc/run_preflight?rev=439651&r1=439650&r2=439651&view=diff
==============================================================================
--- spamassassin/trunk/build/automc/run_preflight (original)
+++ spamassassin/trunk/build/automc/run_preflight Sat Sep 2 14:00:09 2006
@@ -40,35 +40,13 @@
unlink ("ham.log", "spam.log");
-# just the sandbox rules, sandbox plugins, the timing plugin,
-# and the default system-wide plugins (so DNS evals can work)
+# change of plan: mass-check the entire ruleset
#
system ("rm -rf tstrules");
run "mkdir tstrules";
-run "cp ../rules/*.pre tstrules";
-run "cp ../rules/*.pm tstrules";
-run "cp plugins/*.* tstrules";
-
-# don't just copy; instead, transcribe while dropping score and describe lines
-# (to avoid '[26260] warn: config: warning: score set for non-existent rule
-# HTML_SHORT_LENGTH').
-## run "cp ../rules/70_sandbox.cf tstrules";
-open IN, "<../rules/70_sandbox.cf" or die "cannot read ../rules/sandbox.cf";
-open OUT, ">tstrules/70_sandbox.cf" or die "cannot write tstrules/70_sandbox.cf";
-
-while (<IN>) {
- s/^\s+//;
- next if /^(?:
- score|
- describe|
- lang
- )/x;
- print OUT;
-}
-
-close IN or die "close failed!";
-close OUT or die "close failed!";
+run "cp ../rules/*.* tstrules";
+run "cp plugins/*.* tstrules";
# well, ok just those, and anything that's been mailed-in
#