diff options
| author | Michael Orlitzky <mjo@gentoo.org> | 2017-08-04 16:53:48 -0400 |
|---|---|---|
| committer | Michael Orlitzky <mjo@gentoo.org> | 2017-08-04 16:57:07 -0400 |
| commit | 819c3dc8032bf4280c87038a4c408e6cdd218235 (patch) | |
| tree | a630397c8fb9a5f3c089a174ca1ecbfef7945de7 /dev-python/PythonQt/files/PythonQt-3.1-commit-433-441.patch | |
| parent | be5834b9e792665e3c20fc013bae6ab426f73097 (diff) | |
| download | gentoo-819c3dc8032bf4280c87038a4c408e6cdd218235.tar.gz gentoo-819c3dc8032bf4280c87038a4c408e6cdd218235.tar.bz2 gentoo-819c3dc8032bf4280c87038a4c408e6cdd218235.zip | |
mail-filter/spamassassin: new revision without the "bayes" USE flag.
In bug 617950, Deniss Gaplevsky asked that we add Redis support for
the SA bayes engine. I looked into it, and it turns out that the
support is already built-in. That makes things a little weird, because
it would have put us in the position of adding a "redis" USE flag that
does nothing.
Some background will hopefully clarify: when I took over as maintainer
of SA, you were required to choose one of USE="berkdb mysql postgres
sqlite". In other words, bayes support wasn't optional, and you had to
choose a database -- there was no "bayes" USE flag. I don't use bayes,
so I added the "bayes" flag to let me proceed without selecting a
database type.
If I had known about Redis at the time, a better solution would have
been to do what I just did: simply drop the REQUIRED_USE constraint
forcing you to choose one of USE="berkdb mysql postgres sqlite". That
is the end result of this commit, although I had to get rid of the
"bayes" flag now to make it all work.
Gentoo-Bug: 617950
Package-Manager: Portage-2.3.6, Repoman-2.3.1
Diffstat (limited to 'dev-python/PythonQt/files/PythonQt-3.1-commit-433-441.patch')
0 files changed, 0 insertions, 0 deletions
