Re: SA-UPDATE How often new updates?

[Benny Pedersen <me...@junc.org>]

On Tue, March 25, 2008 15:27, Patrick Sherrill wrote:
> Is there any reason not to put the updates in /usr/share/spamassassin using
> sa-update with the --updatedir parameter?

/usr/share/spamassassin < this dir is maintained by some package managers
/var/lib/spamassassin is entirely done by spamassassin :-)

i belive it was the real reason not to overwrite files


Benny Pedersen
Need more webspace ? http://www.servage.net/?coupon=cust37098

Re: SA-UPDATE How often new updates?

[Theo Van Dinter <fe...@apache.org>]

On Tue, Apr 08, 2008 at 11:05:55AM +0200, Benny Pedersen wrote:
> /usr/share/spamassassin < this dir is maintained by some package managers
> /var/lib/spamassassin is entirely done by spamassassin :-)
> 
> i belive it was the real reason not to overwrite files

The slightly longer version:

- originally, sa-update was going to store stuff in /etc/mail/spamassassin (or
  whatever your site rules dir is), in much the same setup as now.  and the
  updates were going to be just that -- updates to the current rule set,
  scores, new rules, etc, but the standard rules would still be used.

- certain folks had issues with something downloading updates to /etc, because
  via the LSB, etc, that kind of stuff goes in /var.

- somewhere in there, it got decided that instead of just updates we should
  allow distribution of the entire rule set.  this allows for people to be
  able to be more flexible with their installations, but also means that
  people need to understand "updates" are really an alternate ruleset (so get
  updates.spamassassin.org if you expect to keep those rules when adding a new
  channel).

So in the end, that's why /usr/share/spamassassin isn't used anymore -- people
have the ability to override the entire standard SA ruleset if they don't want
to use it, and that's why /var is used instead of /usr or /etc.

-- 
Randomly Selected Tagline:
"Flourescent lights are generating negative ions." - Today's BOFH Excuse