public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Torsten Veller <ml-en@veller.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Bogofilter - 0.16.0 - Code Clean-up Release - Phase 1
Date: Fri, 2 Jan 2004 18:06:36 +0100	[thread overview]
Message-ID: <20040102175338.GAe8371.tv@veller.net> (raw)
In-Reply-To: <28CFCD42-3D41-11D8-8D3A-000A95795F3E@stellar.eclipse.co.uk>

* Stroller <stroller@stellar.eclipse.co.uk>:

> so I think Bogofilter-0.16 may be a desirable step to reduce problems
> during `emerge --update`s in the future.

Bogofilter-0.15.13 is in ~ARCH since 29/12. It would be great if
bogofilter-0.15.13 becomes stable as it is announced stable by the
bogofilter devs.

One problem is the new app-text/xmlto dependency:
bogofilter: 
KEYWORDS="~x86 ~ppc ~sparc ~alpha ~hppa ~mips ~arm ~amd64 ~ia64 ~ppc64"
xmlto:
KEYWORDS="x86 ~ppc ~sparc"


> I think that if Bogofilter-0.16.0 were to enter the Portage tree, this
> bug <http://bugs.gentoo.org/show_bug.cgi?id=31800> could also be
> closed.

I think 0.16 can wait a little until 0.15.13 is in ARCH. (0.16 has no
new features. it is only cleaning.)

-- 
.:   Regards Torsten   |      According to the latest official figures,      :.
.:                     |     43% of all statistics are totally worthless.    :.

--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2004-01-02 17:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-02 16:31 [gentoo-dev] Fwd: Bogofilter - 0.16.0 - Code Clean-up Release - Phase 1 Stroller
2004-01-02 16:53 ` [gentoo-dev] Whups! IGNORE ME! " Stroller
2004-01-02 17:02   ` Spider
2004-01-02 17:06 ` Torsten Veller [this message]
2004-01-03  2:27   ` [gentoo-dev] " Mike Gardiner
2004-01-05 13:40 ` [gentoo-dev] Fwd: " Thomas T. Veldhouse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040102175338.GAe8371.tv@veller.net \
    --to=ml-en@veller.net \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox