Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 293061 - Add sa-compile USE flag to mail-filter/spamassassin
Summary: Add sa-compile USE flag to mail-filter/spamassassin
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Gentoo Perl team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-13 16:39 UTC by Tanktalus
Modified: 2014-11-29 10:24 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tanktalus 2009-11-13 16:39:49 UTC
The general idea here is to automatically perform the sa-compile step so that the compiled regexes can be kept up-to-date as I upgrade spamassassin.  Ideally, this would be a step done prior to actually installing, so that it could install as part of the ebuild, of course.

It would also then uncomment the line

loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody

in $ROOT/etc/spamassassin/v320.pre so as to enable the functionality.

Reproducible: Always
Comment 1 Patrick Lauer gentoo-dev 2009-11-13 17:26:37 UTC
Ok, uhm, for which package is this supposed to be? 
Please describe the problem(s) in a way that someone who isn't you has a chance of understanding it :)
Comment 2 Tanktalus 2009-11-13 18:13:27 UTC
ENOCAFFEINE

Sorry about that.
Comment 3 David Abbott (RETIRED) gentoo-dev 2009-11-14 20:31:30 UTC
The file you are referencing says it will not be overwritten during future SpamAssassin installs, why not just edit it yourself?
Comment 4 Tanktalus 2009-11-15 03:52:39 UTC
Maybe I'm being unclear.

The sa-compile step is a post-install step that is optional.  If you do this, then you're also supposed to uncomment the line I referred to earlier.

This absolutely is an optional step.  However, the problem is that if a new regex is added to SpamAssassin, then the library created by an earlier install could be out of date compared to the regexes, and thus not getting the full protection of the new version until I happened to run sa-compile again (which is likely to be forgotten).  If, however, I could perform the sa-compile step as part of the installation of mail-filter/spamassassin, given the USE flag is enabled, then I could know that whatever new regexes that are added would be compiled, or any outdated regexes would no longer be in the library.  And, should I ever stop needing the services of spamassassin, an "emerge -C spamassassin" would clear out this library, too.

The updating of the config file is merely the enabling of the feature that sa-compile makes available, to make it a complete feature.
Comment 5 Benny Pedersen 2013-05-31 00:40:18 UTC
take in note that 3rd patty rule sets is maybe also old rules to remove ? :)

if its planned to work on update spamassassin its complicated, here i do sa-compile each night not just when installing/updateing spamassassin versions
Comment 6 Mikle Kolyada (RETIRED) archtester Gentoo Infrastructure gentoo-dev Security 2014-11-29 10:24:48 UTC
I don't see the point.