-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Duncan Findlay writes:
>On Tue, Dec 13, 2005 at 03:49:44PM -0500, Warren Togami wrote:
>> Duncan Findlay wrote:
>> >The only problem I see with the above, is that no script should be
>> >overwriting rules that are distributed in a package. So if I
>> >distribute a spamassassin-rules .deb, which would stick files in
>> >/usr/share/spamassassin, no script should go in and overwrite those
>> >rules. sa-update should be writing to somewhere in
>> >/var/lib/spamassassin (or /var/cache/spamassassin ?) and
>> >spamassassin/spamd should be reading from that location if it exists.
>> >
>> >So, looks like spamassassin/spamd probably needs to be modified to
>> >read from /var/lib/spamassassin if we want sa-update to work this way.
>> >
>>
>> I am in agreement that sa-update should download rules/scores into
>> somewhere in /var, and it shouldn't overwrite files distributed by the
>> package. I am not so sure I like the separate co-dependent package for
>> scores thing as a requirement.
>
>Right. I also don't see any need to split the rules out of the main
>package -- spamassassin just needs to be smart enough to use the right
>set of rules -- either where sa-update drops them or where they are
>installed by default.
So you're suggesting we'd have:
/usr/share/spamassassin/72_active.cf: base, released copy of
rule updates
/etc/mail/spamassassin/sa_update.cf: override of that default set
??
I could go for that. We'd have to modify the Mail::SpamAssassin code
to recognise the 72_active.cf file somehow and allow it to be ignored
in the system rules dir, if it appears in the site rules dir.
Theo -- comments please.
>> I am a little confused about the terminology, active-set means network
>> tests right?
>
>I believe "active-set" refers to the latest scored set of rules -- the
>idea being that rules will be updated more often than code.
Partly. "Active set" means the latest set of rules and scores that met
the promotion criteria, *excluding the code-tied rules*. When using
sa-update, this is what's in the downloaded tarball. In the development
tree, it's in "rules/72_active.cf". (in other words the sa-update
tarball is simply a copy of that file, tarred+zipped!)
Code-tied rules are excluded because they're 100% dependent on the code in
the Mail::SpamAssassin modules. (their scores will be part of the
sa-update data, however.)
- --j.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFDoHQrMJF5cimLx9ARAgOJAKCGiZOjrSFsEytFS/n33XIeE/DuYACfS81b
A5LtWTBxywEN5q/pJlV8zI4=
=5GKh
-----END PGP SIGNATURE-----
