public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ned Ludd <solar@gentoo.org>
To: Sven Wegener <swegener@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Packages with non-existent herd in metadata.xml
Date: Wed, 06 Oct 2004 14:12:55 -0400	[thread overview]
Message-ID: <1097086374.24468.10337.camel@simple> (raw)
In-Reply-To: <1097085473.4385.4.camel@luna>

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

On Wed, 2004-10-06 at 13:57, Sven Wegener wrote:
> On 2004-10-06 at 11:23 -0400, Ned Ludd wrote:
> > metadata fans might like this patch for emerge.
> > http://dev.gentoo.org/~solar/portage_misc/emerge-metadata-1.332.patch
> 
> You als might want to have a look at my eshowmaintainer I use for
> bug-wrangling. It uses herds.xml to display herd email and maintainers
> of the herd. You might need to adjust the location of the herds.xml.

thanks it does indeed look handy. I'm reinstalling dev-libs/libxml2 with
python support now.

Adding the <longdescription> field </longdescription> when one exists to
that might be nice addition to it's display.

> 
> You can call it with one or several packages on command line or call it
> without arguments to start it in interactive mode.
> 
> Output looks like:
> 
> sven@luna ~ $ eshowmaintainer
> > baselayout
> 
> sys-apps/baselayout
>         Maintainer: azarah@gentoo.org
>         Maintainer: agriffis@gentoo.org
>         Herd: base-system
>                 eMail: base-system@gentoo.org
>                 Maintainer: azarah@gentoo.org
>                 Maintainer: agriffis@gentoo.org
>                 Maintainer: avenj@gentoo.org
>                 Maintainer: drobbins@gentoo.org
>                 Maintainer: gmsoft@gentoo.org
>                 Maintainer: kumba@gentoo.org
>                 Maintainer: lu_zero@gentoo.org
>                 Maintainer: pebenito@gentoo.org
>                 Maintainer: weeve@gentoo.org
>                 Maintainer: seemant@gentoo.org
>                 Maintainer: vapier@gentoo.org
>                 Maintainer: chainsaw@gentoo.org
>                 Maintainer: g2boojum@gentoo.org
> 
> >
> 
> http://dev.gentoo.org/~swegener/tools/eshowmaintainer
-- 
Ned Ludd <solar@gentoo.org>
Gentoo (hardened,security,infrastructure,embedded,toolchain) Developer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-10-06 18:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-27 21:00 [gentoo-dev] Packages with non-existent herd in metadata.xml Sven Wegener
2004-09-28  8:45 ` Paul de Vrieze
2004-09-30  9:49   ` Henrik Brix Andersen
2004-09-30 10:05     ` Paul de Vrieze
2004-09-30 10:24       ` Henrik Brix Andersen
2004-09-28  9:37 ` Michael Cummings
2004-09-28 10:46   ` Robin H. Johnson
2004-09-28 11:02     ` Michael Cummings
2004-09-29 12:39 ` Lisa Seelye
2004-10-06 15:23 ` Ned Ludd
2004-10-06 17:57   ` Sven Wegener
2004-10-06 18:12     ` Ned Ludd [this message]
2004-10-06 19:13 ` Sven Wegener
2004-10-06 19:27   ` Seemant Kulleen
2004-10-06 19:34     ` Sven Wegener

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=1097086374.24468.10337.camel@simple \
    --to=solar@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=swegener@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