The latest stable bogoversion is 0.15.7. This is the ebuild for this version. Attention: The generation of the documentation has changed. It now needs xmlto. But at this time the xmlto.ebuild is broken. Bug 31722. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 19652 [details] latest evolution
If the xmlto bug is resolved, and change of this Bogofilter version improvement hitting the Portage tree..? Today I posted to the Bogofilter mailing list to request some information about a particular behavior; I was advised that: From your query it sounds like you might still be using 0.13.7.2. If so, I'd suggest upgrading to the current stable release which is 0.15.7. It has lots of improvements, does a better job, and is faster. Thanks, Stroller.
Hi Stroller, i read your mail on the bogofilter list. xmlto compiles fine, the html documentation gets generated. Everything seems to be fine. You can use the updated ebuild (see below). The ebuild for the next bogofilter version will have support for tdb (i hope ;)
Created attachment 21564 [details] update corrected xmlto dependency - bogofilter-faq gets installed anyway
This one can be closed. xmlto is stable for x86 and a newer bogofilter version is in portage.
Tested the bogofilter-0.15.7.ebuild above & it has been working fine for some days. Today I emerged the bogofilter-0.15.13.ebuild that is ~86 in the Portage tree & have run basic tests on it. It pulls in 3 other (xml?) packages as dependencies, but seems to be working fine. I am looking forward to this becoming stable - it is important for Gentoo x86 (& other stable arches) users of Bogofilter to be able to migrate onto a version with a single wordlist, as the separate-wordlists of 0.13.7.2 (currently the latest marked stable in Portage) will be depreciated. IMO the issue of separate -> single wordlists should be added to einfo / ewarn in the eBuild.
> It pulls in 3 other (xml?) packages as dependencies, These are dependencies of xmlto (app-text/docbook-xml-dtd, docbook-xsl-stylesheets, libxslt). You only need them at build time and only if you want html documentation. So you can unmerge them again if you don't need them. You can also change the ebuild as follows (see my alternativ 0.15.13 ebuild, which they don't want) IUSE="" ---> IUSE="doc" ...and... app-text/xmlto ---> doc? ( app-text/xmlto ) configure checks if xmlto is installed, yes: html-docu is generated, no: html-docu is not generated. > IMO the issue of separate -> single wordlists should be added to einfo / ewarn in the eBuild. Do you think this can wait until the bogofilter-0.16 version? 0.16 is the version where 'a number of features have been deprecated'. See the RELEASE INFOs of that version. Because of the other changes, do you think that this one is special? I think they all break your installation if you depend on them.
OLD
