metadata.xml (the second)

As I was kinda bored after work today, I had a closer look at what I saw during my fuckup in the morning. Well, Steve said, that when he looked at metadata.xml it’d be “really common” .. still that isn’t making it right ..

There is a reason we do have a herds.xml (exactly for the reason to associate people with packages, and that’s what the <herd> tag is for in metadata.xml) file. So after a preliminary look through the repository, here are the winners:

Don’t know how accurate that list is, but you can check it for yourself. The commands I’ve used are these:

While herds.list holds a list (separated by n) with all the herds there are. The raw files are here and here and here. Knock yourself out!

5 thoughts to “metadata.xml (the second)”

  1. We use the maintainer tag for herds when the bugzilla alias is not just the name of the herd.

    This is the case for perl (perl-bugs@gentoo.org) which explain it being top of the list.

    Me and Jakub (and others) will hate you if you revert that.

  2. > We use the maintainer tag for herds when the bugzilla alias is not just the name of the herd.

    I know that pretty well Diego, but then again; there’s tools to look it up. Sure it’s faster, if you put the data again into metadata.xml, but they *really* belong into herds.xml.

  3. There is a simple solution to fix this mess once and for all: get rid of the herd concept and use mail aliases directly. It’s just an IMO useless layer of indirection that has been causing confusion since it was implemented.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.