summaryrefslogtreecommitdiff
path: root/mail/spamassassin/patches/patch-bc
diff options
context:
space:
mode:
Diffstat (limited to 'mail/spamassassin/patches/patch-bc')
-rw-r--r--mail/spamassassin/patches/patch-bc32
1 files changed, 32 insertions, 0 deletions
diff --git a/mail/spamassassin/patches/patch-bc b/mail/spamassassin/patches/patch-bc
new file mode 100644
index 00000000000..023f87adafd
--- /dev/null
+++ b/mail/spamassassin/patches/patch-bc
@@ -0,0 +1,32 @@
+$NetBSD: patch-bc,v 1.1 2007/08/26 17:26:51 heinz Exp $
+
+ Both submitted upstream:
+ - no need for a hard-coded path, the appropriate variables already exist
+ - the documentation conflicts with the code
+
+--- sa-compile.raw.orig 2007-08-08 15:19:47.000000000 +0200
++++ sa-compile.raw
+@@ -661,7 +661,7 @@ Options:
+ --siteconfigpath=path Path for site configs
+ (default: /etc/mail/spamassassin)
+ --updatedir=path Directory to place updates
+- (default: /var/lib/spamassassin/compiled/<version>)
++ (default: @@LOCAL_STATE_DIR@@/compiled/@@VERSION@@)
+ --cf='config line' Additional line of configuration
+ -D, --debug [area=n,...] Print debugging messages
+ -V, --version Print version
+@@ -719,12 +719,12 @@ the default directories (usually C</etc/
+
+ By default, C<sa-compile> will use the system-wide rules update directory:
+
+- @@LOCAL_STATE_DIR@@/spamassassin/compiled/@@VERSION@@
++ @@LOCAL_STATE_DIR@@/compiled/@@VERSION@@
+
+ If the updates should be stored in another location, specify it here.
+
+ Note that use of this option is not recommended; if sa-compile is placing the
+-compiled rules the wrong directory, you probably need to rebuild SpamAssassin
++compiled rules in the wrong directory, you probably need to rebuild SpamAssassin
+ with different C<Makefile.PL> arguments, instead of overriding sa-compile's
+ runtime behaviour.
+