On 04/07/10 14:00, Ben de Groot wrote:
> On 7 April 2010 13:20, Sebastian Pipping <sp...@gentoo.org> wrote:
>> - herds.xml does not hold membership lists for
>> all projects, not even herds. The load
>> evaluator needs access to complete mappings
>> to generate output close to reality.
>> How can such a mapping be made without
>> duplicating data?
>
> herds.xml should be the definitive resource for herds, so any herds
> that are not on there should be added, and outdated information should
> be brought up to date.
they are in there but keep their member list elsewhere.
an example is herd "bsd":
<herd>
<name>bsd</name>
<email>b...@nospam</email>
<description>Support for *BSD system packages,
and *BSD derived packages.</description>
<maintainingproject>
/proj/en/gentoo-alt/bsd/index.xml
</maintainingproject>
</herd>
now that i have a closer look maybe the herds itself are manageable,
besides the annoyance of being in another CVS tree:
<subproject ref="/proj/en/gentoo-alt/bsd/obsd/index.xml"
inheritmembers="yes" />
<subproject ref="/proj/en/gentoo-alt/bsd/fbsd/index.xml"
inheritmembers="yes" />
<subproject ref="/proj/en/gentoo-alt/bsd/nbsd/index.xml"
inheritmembers="yes" />
<dev role="lead">welp</dev>
<dev role="lead" description="Deputy lead">drizzt</dev>
<dev role="member">aballier</dev>
<dev role="member">the_paya</dev>
that looks usable.
with the herd "embedded" it's difficult though: the page
<http://www.gentoo.org/proj/en/base/embedded/index.xml>
lists members for it but the page source does not
hold it, explicitly. where does it come from?
> Other projects should have membership listed on their project pages.
> Again, where these are outdated, they should be brought up to date.
seems like they use the same syntax, too. i start to like guidexml :-)
some of the mail aliases i don't handle yet, could also be a problem
(especially those i don't have permission to look at).
sebastian
