I've been doing something along those lines in the tinderbox scripts, using xmlstarlet; if Portage could just use Python to fetch the data from metadata, and maybe abide to restrictions, it would be a tremendously nice thing...
Is showing it right at the beginning of the log ok too?
>>> Emerging (1 of 1) x11-drivers/nvidia-drivers-195.36.24
* NVIDIA-Linux-x86_64-195.36.24-pkg2.run RMD160 SHA1 SHA256 size ;-)
* checking ebuild checksums ;-)
* checking auxfile checksums ;-)
* checking miscfile checksums ;-)
* CPV: x11-drivers/nvidia-drivers-195.36.24
* REPO: gentoo
* Maintainer: firstname.lastname@example.org email@example.com,firstname.lastname@example.org,none
* USE: acpi amd64 elibc_glibc gtk kernel_linux multilib userland_GNU
Since I assumed you want to copy and paste this, I formatted it as: "the first maintainer (if present, otherwise the first herd) followed by a whitespace, followed by a comma separated list of maintainers and herds". (Follows the rule stated on the bug wranglers page .)
If the metadata.xml file follows the dtd , only emails will be listed for maintainers. If the herds are present in $PORTDIR/metadata/herds.xml, herds will be replaced by emails too.
 http://www.gentoo.org/proj/en/qa/bug-wranglers/index.xml (Section 4, topic 'Assigning Bug Reports')
Looks good to me, yup; can Portage fetch herds.xml by itself at some point, maybe with --sync?
(In reply to comment #2)
> Looks good to me, yup; can Portage fetch herds.xml by itself at some point,
> maybe with --sync?
herds.xml is already synced by emerge --sync.
Ah I didn't know... then it looks absolutely cool :)
maybe it makes more sense (also) to show this in the die message in the "!!! When you file a bug report" section? Sort of as suggestion who to assign it to.
Not that much of a good idea because users can't reassign it by themselves...
hmmm, ok, didn't know that.
This is in git now:
This is fixed in 188.8.131.52 and 2.2_rc76.