From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 80E10139694 for ; Tue, 9 May 2017 14:52:40 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A6F52E0D82; Tue, 9 May 2017 14:52:38 +0000 (UTC) Received: from smtp.gentoo.org (mail.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7D8F2E0D82 for ; Tue, 9 May 2017 14:52:38 +0000 (UTC) Received: from oystercatcher.gentoo.org (unknown [IPv6:2a01:4f8:202:4333:225:90ff:fed9:fc84]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 0C41034168E for ; Tue, 9 May 2017 14:52:37 +0000 (UTC) Received: from localhost.localdomain (localhost [IPv6:::1]) by oystercatcher.gentoo.org (Postfix) with ESMTP id 5842B73F3 for ; Tue, 9 May 2017 14:52:35 +0000 (UTC) From: "Michael Orlitzky" To: gentoo-commits@lists.gentoo.org Content-Transfer-Encoding: 8bit Content-type: text/plain; charset=UTF-8 Reply-To: gentoo-dev@lists.gentoo.org, "Michael Orlitzky" Message-ID: <1494341507.ddeb03794d7efd423398bc175b824ea158102578.mjo@gentoo> Subject: [gentoo-commits] repo/gentoo:master commit in: mail-filter/spamassassin/ X-VCS-Repository: repo/gentoo X-VCS-Files: mail-filter/spamassassin/metadata.xml X-VCS-Directories: mail-filter/spamassassin/ X-VCS-Committer: mjo X-VCS-Committer-Name: Michael Orlitzky X-VCS-Revision: ddeb03794d7efd423398bc175b824ea158102578 X-VCS-Branch: master Date: Tue, 9 May 2017 14:52:35 +0000 (UTC) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-commits@lists.gentoo.org X-Archives-Salt: c6a6ffe1-6290-4315-a92d-404351a143f8 X-Archives-Hash: 60f3e7ecc9c64abad0b8ae0d8556e656 commit: ddeb03794d7efd423398bc175b824ea158102578 Author: Michael Orlitzky gentoo org> AuthorDate: Tue May 9 14:51:47 2017 +0000 Commit: Michael Orlitzky gentoo org> CommitDate: Tue May 9 14:51:47 2017 +0000 URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ddeb0379 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 mail-filter/spamassassin/metadata.xml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/mail-filter/spamassassin/metadata.xml b/mail-filter/spamassassin/metadata.xml index e62f9a74939..e2f64879e90 100644 --- a/mail-filter/spamassassin/metadata.xml +++ b/mail-filter/spamassassin/metadata.xml @@ -24,7 +24,9 @@ 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). Install a cron job to update SpamAssassin's rules daily.