Am 30.11.2014 um 19:48 schrieb Ted Mittelstaedt:
On 11/29/2014 8:39 PM, John Hardin wrote:if that rule can't work in most environments and not made conditionally it has to be dropped at all because it has more drawbacks than benefitsIt has already been commented out in my sandbox. But this effectively means we cannot add new features to SA conditionals because they might do this to older installs.No, just release patches to the older versions to Conf.pm and Parser.pm These are not COMPILED modules so it is easy to patch them. The people who even notice the warnings are going to be competent enough to run patch, and for the people who are running SpamAssassin who aren't competent enough to be able to do that, I doubt they will be noticing log entries
stop that polemic! competent people would not patch files from a RPM packagethe solution is not to publish rules not working on the last official SA upstream version
[root@mail-gw:~]$ rpm -q --file /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Conf.pm
spamassassin-3.4.0-7.fc20.x86_64
signature.asc
Description: OpenPGP digital signature
