Am 30.11.2014 um 21:49 schrieb Dave Pooser:
On 11/30/14, 2:04 PM, "Reindl Harald" <h.rei...@thelounge.net> wrote:it's *not* about a "crufty version of perl" it's about a perl version check not existing in SpamAssassin 3.4.0 it's visible on recent perl versions without the version checks issing the warnings they had no problemOK, I could have been clearer there. Let me spell out my logic: 1) Red Hat is not going to release a new version of SpamAssassin for their existing distros. That's not how they roll. 2) Any rule that uses a regex that requires a version of Perl later than the 2006-era Perl 5.8.8 will cause a fatal sa-update error unless it's wrapped in a version check 3) Using version_check creates a non-fatal warning on versions of SA =< 3.4.0 So, we have three options 1) Force Red Hat users to endure a warning unless they update their spamassassin outside of normal distro channels to gain version_check capabilities 2) Take the version_check out and break sa-update on computers running older versions of perl 3) Write all spamassassin rules to use the lowest-common-denominator perl, which would be the "crufty version of perl" I referred to above. Do you see a fourth option?
4) don't publish a rule with a 0.001 score introducing problems the impact of that rule can't beat out the cron-mails at all 5)make the condition to the SA version, there are already ton's of "if (version >= 3.004000)" rules and so it needs just to depend on SA bigger than 3.4.0 instead of the perl check
why that would work? well, older RHEL versions as you said won't upgrade SA or perl that setups would not use the rule, recent ones would
signature.asc
Description: OpenPGP digital signature
