public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nathan Phillip Brink <ohnobinki@ohnopublishing.net>
To: gentoo-dev@lists.gentoo.org
Cc: funtoo-dev@googlegroups.com, gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [funtoo] [bugzilla-daemon-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org: [Bug 322157] [mail-filter/procmail] new ebuild + autocreate maildirs]
Date: Mon, 12 Jul 2010 01:25:41 -0400	[thread overview]
Message-ID: <20100712052540.GI14243@ohnopublishing.net> (raw)
In-Reply-To: <20100707180349.32a1b2e5@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]

On Wed, Jul 07, 2010 at 06:03:49PM -0600, Ryan Hill wrote:
> On Thu, 8 Jul 2010 00:56:52 +0200
> Enrico Weigelt <weigelt@metux.de> wrote:
> 
> > 
> > Hi folks,
> > 
> > 
> > YFYI: yet another of my ebuilds kicked-down.
> > 
> > It's an improved version of procmail, which automatically creates
> > missing maildir directories.
> 
> Upstream first (TM).

I'm pretty sure that the main problem with procmail is that its upstream is quite dead. The proper solution might be simply a fork of procmail by someone who is willing to accept and apply distros' patches. This would be completely independent of distributions... or could be similar to Fedora (or a Fedora maintainer) starting up tigervnc. The problem with this approach would be getting enough momentum behind it and having distributions recognize such a fork.

I was myself interested in pushing a patch (unfortunately it's still unfinished :-/) to procmail's upstream, but had trouble finding the upstream. If anyone has had better luck or knows of a fork like I describe above, I'd be interested. Of course, knowing that there is an upstream to submit such a patch to would be a great encouragement for me to finish writing it. ;-)

-- 
binki

Look out for missing or extraneous apostrophes!

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-07-12  5:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-07 22:56 [gentoo-dev] [bugzilla-daemon@gentoo.org: [Bug 322157] [mail-filter/procmail] new ebuild + autocreate maildirs] Enrico Weigelt
2010-07-07 23:11 ` Samuli Suominen
2010-07-10 16:13   ` Enrico Weigelt
2010-07-11  5:28     ` Jacob Godserv
2010-07-11  7:01       ` Hans de Graaff
2010-07-11  7:09         ` Enrico Weigelt
2010-07-11  8:58           ` Nirbheek Chauhan
2010-07-11  9:51             ` [gentoo-dev] " Duncan
2010-07-11  9:53             ` [gentoo-dev] " Enrico Weigelt
2010-07-11 10:28               ` Nirbheek Chauhan
2010-07-11 16:53                 ` Jorge Manuel B. S. Vicetto
2010-07-12  2:54                   ` Enrico Weigelt
2010-07-12  2:44                 ` Enrico Weigelt
2010-07-12 11:55                   ` Nirbheek Chauhan
2010-07-15 13:43                     ` Enrico Weigelt
2010-07-08  0:03 ` [gentoo-dev] Re: [funtoo] [bugzilla-daemon-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org: " Ryan Hill
2010-07-12  5:25   ` Nathan Phillip Brink [this message]
2010-07-08  1:36 ` [gentoo-dev] [bugzilla-daemon@gentoo.org: " Robin H. Johnson
2010-07-10 16:07   ` Enrico Weigelt
2010-07-08  2:38 ` [gentoo-dev] Re: [funtoo] [bugzilla-daemon-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org: " Paul Arthur

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=20100712052540.GI14243@ohnopublishing.net \
    --to=ohnobinki@ohnopublishing.net \
    --cc=funtoo-dev@googlegroups.com \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-user@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