!!Version 0.16 is a current-version right now!! Bogofilter-0.15.13 is the stable version. "Code Clean-up Release - Phase 1" It is time to clean house! "The goal of the bogofilter 0.16 series is to clean out this excess code and create a core of high quality code. This will necessarily cut some ties with previous versions, and you may need to adjust your wrapper scripts to make up for features we have dropped." Reproducible: Always Steps to Reproduce:
Created attachment 23011 [details] bogofilter-0.16.0.ebuild
Created attachment 23012 [details] bogofilter-0.16.0.ebuild with tdb useflag support for dev-libs/tdb
Well, I use this, looks like for most people 0.16 w/o the deprecated stuff will be fine, sticking it in unstable, hopefully nobody will kill me.
Wait, what is the tdb useflag? I don't see it in the use.desc ... Can't just go creating useflags...
Created attachment 24476 [details] bogofilter-0.16.4.ebuild with a 'doc' useflag (!) !!Version 0.16.4 is a current-version right now!! Bogofilter-0.15.13.1 is the stable version. So it would be better to push 0.15.13 to stable before looking at that one. > Wait, what is the tdb useflag? I don't see it in the use.desc ... > Can't just go creating useflags... See #35430. Well as i got no comment until now and because tdb is siad to be slow and unsupported i dropped that use flag again -- and took the choice from the user. Last week i asked seemant to mark 0.15.13.1 as stable via email. I got no reply so i can only guess: Maybe the time in ~ARCH was too short, maybe my wish for using 'doc' as useflag was an abuse of useflags. "app-text/xmlto is a buildtime dependency. It is only needed for the html documentation but xmlto needs the following packages, which are not needed on a (well, my) server: dev-libs/libxml2-2.6.4 dev-libs/libxslt-1.1.2 app-text/docbook-xsl-stylesheets-1.62.4 app-text/docbook-xml-dtd-4.2 While there are still the man pages i would like to use the "doc" useflag. I attached the prefered ebuild. No further changes are needed because configure checks if xmlto is installed, if it is installed html docs are generated, if xmlto is not installed, the html docs are not generated. There is a faq which needn't be generated. I would leave it because the information is unique. Then again i commented the doc/programmer part out -- it is only needed for other OS (like RISC OS, FreeBSD, hp-ux)" Attached is the ebuild for 0.16.4 (unstable!) with 'doc' (which is new to bogofilter - and maybe needs some discussion?)
Hmm... OK, I think I'm a bit confused about all of this, I think 'doc' is generally used to specify 'extra documentation' the man pages should be installed regardless. I would _love_ if you could fix up the ebuild to depend on xmlto with doc? and always install the man pages. Then the ebuild will be entirely ready to commit to unstable (I'm using it on my server already and it is working great) Thanks! (and more likely the reason you didn't get a response about 0.15.3.1 is because seemant is busy, I'll see abouut stabilifying it after I can get some feedback.)
Brandon, i sent you a mail -- hope you got it. Today, bogofilter-0.16.4 is officially marked stable. Here is an excerpt from the bogofilter message: Bogofilter-0.16.4 has been promoted from "current" to "stable". The 0.16.x release series is officially known as "Code Clean-up Release - Phase 1". Unofficially it's known as the "deprecated code release". A lot of old compatibility code has been bracketed by "#ifdef ENABLE_DEPRECATED_CODE" and "#endif" statements. By default bogofilter will build with this code disabled. If you _must_ have the old code enabled, use "configure --enable-deprecated-code". File RELEASE.NOTES-0.16 has details of the changes. If you haven't read it already, do so!
hmm... need to get xmlto into ~arm ~mips and ~ppc64 UGH
Committing...
