On Fri, 2004-01-02 at 14:11, Lincoln A. Baxter wrote: > 3.) I have developed an ebuild for the perl interface to the Xerces-c > XML parser. Which is a bit of a pain to build. The Gentoo guides for > submitting ebuilds says that the "perl herders" need to approve such > ebiulds. Well, they do not even tell you how to send mail to the perl > herders. (No link, no nothing). So I have a perfectly good ebuild for > perl's XML-Xerces module in my portage overlay dir, that I have not > submitted, because of my experience with bug 21580, and my inability to > find the "perl herders".
You already found the link, but the answer to finding who is in a herd is the page http://www.gentoo.org/proj/en/metastructure/herds/herds.xml This link can be found from the page http://www.gentoo.org/proj/en/metastructure/herds/ which is mentioned in the file /usr/portage/skel.metadata.xml Which I discovered along with other skeleton files mentioned in the Ebuild Howto. Was this easy to find? In my case, the answer was yes. I was trying to make sure that I dotted the i's and crossed the t's, etc for an ebuild that I was creating, so I was reading everything that I could find. Since there was a link inside of the skeleton file, I went and read the page. Now having said that, there is a lot of developer/project documentation that isn't linked to from the Docs page. It would be really nice to have those links available. (I'm making the assumption that documentation that is publicly accessible on the server should be able to be found from the docs page, If it shouldn't be read by the public, then my opinion is that is should not be publicly accessible and should be protected) I've managed to find some of those links by lurking on the gentoo-dev mailing list and from articles in the GWN, but I'm sure that is a lot that I would be interested in reading that I don't know about. -- My Gentoo stuff: http://varnerfamily.org/pvarner/gentoo -- [EMAIL PROTECTED] mailing list
