On 6/14/06, Chris Gianelloni <[EMAIL PROTECTED]> wrote:
On Wed, 2006-06-14 at 22:34 +0200, Jakub Moc wrote:
> > It's not irrelevant; you're just not reading it properly. You might
> > notice that metadata.xml contains tags other than <herd>, like, say,
> > <maintainer>. In the example that sparked this, <herd> is games and
> > <maintainer> the individual dev who maintains it. Simple enough, no?
>
> Please, go through the tree and see at least so many metadata.xml files
> as I have seen, before claiming something that simply doesn't reflect
> current practice. There are many ebuilds with no <maintainer> tag and
> <herd> only. Are you claiming that they are unmaintained? Well, that
Nobody said that they were unmaintained. Again, why do people *insist*
on trying bullshit arguments like this? "Are you claiming.." No, he's
not claiming that, or he would have *said* that.
> obviously doesn't match the reality. So, if they actually _are_
> maintained by the relevant herd, then you shouldn't dump stuff on that
> herd without discussing it w/ them first. I'm pretty sure mcummings will
> gladly explain to you what will happen if you do, as well as a bunch of
> other devs... :P
A herd is a group of packages, not a listing of people. When you get
information from the herds.xml, you are getting the listing of the
people that *maintain* that herd. You are not getting a listing of the
people *in* the herd.
According to the devmanual [1]
"A herd is a collection of developers who maintain a collection of
related packages"
are you sure you are using the correct term?
[1] http://devmanual.gentoo.org/general-concepts/herds-and-projects/index.html
Please go back and read the herds project page[1] and try to understand
this. It really is printed quite simply.
> To make it pretty clear and explicit - bugs gets assigned to
> <maintainer> (if there's any in metadata.xml), and get CCed to <herd>
> (if there's any in metadata.xml). If there's no <maintainer>, whoever is
> in <herd> will get that bug assigned and can happily smack you butt once
> they've find out you've dumped the package on them without their
> knowledge... That's how the large part of current ~600 dev-perl/*
> ebuilds has made it into the tree and that mistake doesn't need to be
> repeated.
You are correct. This is *exactly* how it works. Also, you'll notice
that nothing either I or Stephen has said contradicts this, if you
actually went back and contemplated what we both said.
[1] http://www.gentoo.org/proj/en/metastructure/herds/
--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQBEkIGskT4lNIS36YERAlg2AKCmitk2Pwd7XSP+ysarJDc1imbnUgCgt2wv
OYJuhhIg+vG5wom7DRcwHEg=
=Tprl
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
