On Wed, Jun 06, 2007 at 09:35:48PM -0400, Joey Hess wrote: > The docs are not really clear on how sa-compile is integrated with the > rest of the package. After reading them I was left wondering:
> 1. Will a compiled ruleset prevent an upgraded ruleset from being seen? > I see that the compiled ruleset is put in a versioned directory in > /var, but I'm unsure that would happen if a rule was changed w/o the > upstream version changing. I *think* the plugin will run the un-compiled rule if there isn't a correspoding compiled rule. I have not tested this (and will before updating the doc of course...). > 2. If I enable the cron job, will it compile the ruleset every day for > me? (I read the code and found it does, although it also /dev/nulls any > errors, which I don't like.) sa-compile is very verbose. It might be possible to only /dev/null STDOUT. (I don't know if it spews useless stuff on STDERR...) Again, I'll test this. > 3. What do I need to do on upgrade? Apparently the postinst does not run > sa-compile, so it seems I'd need remember to run sa-compile by hand > unless I enable the cron job. IMHO, it would be good to run > sa-compile in the postinst if re2c is available and > /var/lib/spamassassin/compiled exists. That's a good point. Not an issue in this release I suppose since there's already a manual step, but something I forgot about. :-) > BTW, the README.Debian has some old text about sa-update being manual > and "quite new", which seems outdated now that there's a cron job. Thanks; I'll update that too. -- Duncan Findlay
pgpepSNqAdxUF.pgp
Description: PGP signature
