https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6644
--- Comment #9 from Kevin A. McGrail <[email protected]> 2011-10-31 16:45:33 UTC --- > Seems to work. (dont' forget to mkdir /root/sa-update ) > > So is this recommended for people running trunk? I think it would be better > if > a normal sa-update just worked, with scores. But I guess I don't understand > the need for the way it's currently working. My understanding is: If you want to use trunk in a production environment, you need rules. Using the rules that come with trunk, you are using rules designed for the mass-checker to figure out the best scoring algorithmically. Perhaps we should add a quick script called svn-trunk-get-rules-for-production.sh with commands such as this to svn for trunk? REV=`dig +short TXT 2.3.3.updates.spamassassin.org|tr -d '"'`; mkdir /root/sa-update; wget -P /root/sa-update/ http://buildbot.spamassassin.org/updatestage/${REV}.tar.gz http://buildbot.spamassassin.org/updatestage/${REV}.tar.gz.asc http://buildbot.spamassassin.org/updatestage/${REV}.tar.gz.sha1 && sa-update --install /root/sa-update/${REV}.tar.gz It'll need some text re: the purpose of the script as well so it can be updated for example to use 0.4.3 when the next release comes out. It could be refined for a few minutes to check for wget vs. curl, etc. as well as just document the manual steps if needed. But the number of people running trunk in production is small so if this is documented, that might be enough. So perhaps a command in sa-update that is something like --svn-trunk-get-rules-for-production is a better idea? Then have that load the last releases rules. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
