There doesn't seem to be much interest in keeping the Portage tree up-to-date with the current releases of Bogofilter, however development of it is moving quite rapidly & it is at a stage now at which I believe the ebuild *should* be updated, if it is intended to remain in Portage.
From what I have heard of Spamassasin it uses several methods to detect spam (including blacklists based upon the reports of other users?), and I choose Bogofilter because it's relies purely upon Bayesian analysis of MY spam messages. So I would like to see Bogofilter remain current within Gentoo.
I have forwarded below an email from Bogofilter's maintainer to the Bogofilter mailing list giving some outlines of why I think an update is needed at present. It's particularly worth noting that the present version of Bogofilter within the tree (0.13.7.3) uses two separate wordlists for spam & ham. Current releases use by default a *single* wordlist of tokens with a pair of spam/ham counts - the separate wordlists are depreciated, and the code will be removed in 0.17.x, so I think Bogofilter-0.16 may be a desirable step to reduce problems during `emerge --update`s in the future.
If any interested &/or helpful dev could take a look at <http://bugs.gentoo.org/show_bug.cgi?id=37017> I would be much indebted. To give you a head-start on the New Year's bug-fixing league-table, I think that if Bogofilter-0.16.0 were to enter the Portage tree, this bug <http://bugs.gentoo.org/show_bug.cgi?id=31800> could also be closed.
Many thanks for your time & bandwidth,
Stroller.
Begin forwarded message:
From: David Relson <[EMAIL PROTECTED]> Date: January 1, 2004 10:55:19 pm GMT To: bogofilter <[EMAIL PROTECTED]> Subject: Bogofilter - 0.16.0 - Code Clean-up Release - Phase 1
Greetings,
Bogofilter-0.16.0 is the new "current" release. It is officially the "Code Clean-up Release - Phase 1". Unofficially it's known as the "deprecated code release".
The main change is that a lot of old compatibility code is now bracketed by "#ifdef ENABLE_DEPRECATED_CODE" and "#endif" statements. By default bogofilter will build with this code disabled. If you need it, use "configure --enable-deprecated-code".
A second change is that the binary rpms are now built with BerkeleyDB
4.1. If you have an older version of BerkeleyDB, you will need to build
bogofilter from source. Configure option "--with-libdb-prefix={path}"
will likely be needed.
File RELEASE.NOTES-0.16 has details of the changes. It is recommended reading!!
A new file, diff.01513.0160.bz2 has a context diff ("diff -c") between the previous stable release, bogofilter-0.15.13, and this release. ... Happy New Year!
David
--------------------------------------------------------------------- FAQ: http://bogofilter.sourceforge.net/bogofilter-faq.html To unsubscribe, e-mail: [EMAIL PROTECTED] For summary digest subscription: [EMAIL PROTECTED] For more commands, e-mail: [EMAIL PROTECTED]
-- [EMAIL PROTECTED] mailing list
