mail-filter/spamassassin: update description of USE=bayes flag.

A user asked us to enable Redis support for SpamAssassin in bug
617950, but it should already be there. SpamAssassin has its own
"TinyRedis" client, and doesn't pull in any extra dependencies to
enable it.

This is somewhat confusing when you look at the REQUIRED_USE for
SpamAssassin, which suggests that, to enable USE=bayes, you need to
pick a particular database. I only see three solutions, none of which
are great:

  1. Introduce a USE=redis flag that does nothing.

  2. Try to document the USE=bayes flag better, to make it clear
     that you get Redis support even with USE="-bayes".

  3. Allow USE=bayes without picking a database driver.

The first I've ruled out for aesthetic reasons, and the third I think
could do more harm than good (to everyone who wants bayes without
Redis). Therefore I've taken the second option, and updated the
documentation for the local USE=bayes flag. It now mentions that you
don't need USE=bayes to get the Redis bayes backend -- it's always
there.

Gentoo-Bug: 617950

Package-Manager: Portage-2.3.3, Repoman-2.3.1

1 files changed, 3 insertions, 1 deletions

diff --git a/mail-filter/spamassassin/metadata.xml b/mail-filter/spamassassin/metadata.xml
index e62f9a749397..e2f64879e901 100644
--- a/mail-filter/spamassassin/metadata.xml
+++ b/mail-filter/spamassassin/metadata.xml
@@ -24,7 +24,9 @@
   <use>
     <flag name="bayes">
       Require a database (MySQL, SQLite, Postgres, or BerkDB) backend
-      to enable the Bayesian filtering database.
+      to enable the Bayesian filtering database. If you use the Redis
+      backend, you do not need to enable this flag (Redis support is
+      enabled automatically, and has no external dependencies).
     </flag>
     <flag name="cron">
       Install a cron job to update SpamAssassin's rules daily.