ports/108934: mail/p5-Mail-SpamAssassin: spamassassin uses /var/lib/spamassassin directory but /var/lib doesn't exist on FreeBSD

Matus UHLAR - fantomas uhlar at fantomas.sk
Sun Mar 18 15:10:08 UTC 2007


The following reply was made to PR ports/108934; it has been noted by GNATS.

From: Matus UHLAR - fantomas <uhlar at fantomas.sk>
To: Michael Scheidell <scheidell at secnap.net>
Cc: bug-followup at FreeBSD.org
Subject: Re: ports/108934: mail/p5-Mail-SpamAssassin: spamassassin uses /var/lib/spamassassin directory but /var/lib doesn't exist on FreeBSD
Date: Sun, 18 Mar 2007 16:06:03 +0100

 > Matus UHLAR - fantomas wrote:
 > >run sa-update. It will create
 > >/var/lib/spamassassin/<version>/updates_spamassassin_org/ directory, where
 > >it puts updated rules, if it founds them. spamassassin and spamd later 
 > >check
 > >these rules instead of those in /usr/local/share/spamassassin/50_scores.cf
 > >
 > >You may need older installation of spamassassin to verify this, I'm not 
 > >sure
 > >that 3.1.8 has some updates, but I was able to update rules for 3.1.7 at
 > >least twice.
 
 On 14.03.07 08:53, Michael Scheidell wrote:
 > I think some of this was discussed on SpamAssassin list.
 > If you actually let sa-update put the files in /var/lib/spamassassin, it 
 > REPLACES original files.
 
 original files are in /usr/local/etc/mail/spamassassin/, but if there are any
 updates in $LOCALSTATEDIR/..., spamassassin and spamd ignore those from
 installation.
 
 > I think the suggestion was to run sa-update like this:
 > 
 > sa-update --updatedir /usr/local/share/spamassassin
 
 that is possible, but I prefer to keep files installed with spamassassin
 available. It's good to use updates directory in /var, but
 /var/lib/spamassassin/ seems not to be the best idea for FreeBSD...
 
 > my suggestion to patch sa-update to do that was not met with enthusiasm.
 > 
 > try the above, things should work better, and I will look at patching 
 > sa-update for the ports only.
 
 actually, I don't mind have /var/lib/spamassassin on my filesystem, I just
 think that's not good idea because of FreeBSD's different directory layout.
 for ports, you could just specify localstatedir when configuring
 SpamAssassin. However as I said, I would prefer different directory for
 updates than the one in /usr/local/...
 
 -- 
 Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/
 Warning: I wish NOT to receive e-mail advertising to this address.
 Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
 Atheism is a non-prophet organization. 


More information about the freebsd-perl mailing list