1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
|
$NetBSD: patch-bc,v 1.3 2008/06/22 22:41:01 heinz Exp $
Both submitted upstream (bug id 5628/5630):
- no need for a hard-coded path, the appropriate variables already exist
- the documentation conflicts with the code
--- sa-compile.raw.orig 2008-06-10 11:21:07.000000000 +0200
+++ sa-compile.raw
@@ -684,7 +684,7 @@ Options:
--siteconfigpath=path Path for site configs
(default: /etc/mail/spamassassin)
--updatedir=path Directory to place updates
- (default: /var/lib/spamassassin/compiled/<perlversion>/<version>)
+ (default: @@LOCAL_STATE_DIR@@/compiled/@@PERL_MAJOR_VER@@/@@VERSION@@)
--cf='config line' Additional line of configuration
-D, --debug [area=n,...] Print debugging messages
-V, --version Print version
@@ -746,12 +746,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/@@PERL_MAJOR_VER@@/@@VERSION@@
+ @@LOCAL_STATE_DIR@@/compiled/@@PERL_MAJOR_VER@@/@@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.
|
