[Rpm-metadata] xml update

[seth vidal]

> > If they ARE used b/t multiple depsolvers the sure. But I don't think
> > anyone wants the union of all things that _COULD_ be used by more than
> > one depsolver - and that's what you're talking about here. Not a
> > graceful intersection with namespaces for desired other areas.
> 
> "Can", for "obvious" cases. The fact that none of the current depsolvers
> support something that another depsolver supports has something to do
> with the fact that there's no common metadata?
> 

does it?  if it were as common as is being suggested then others would
have implemented it in their metadata. right?


> For a example I see Enhances & Suggests as something which would be
> useful for many depsolvers. Installing xmms? You know, this only gives
> you ogg support, you probably want to play mp3's as well, should I
> install xmms-mp3 for you as well?

but where do we get that data from?
When building the file - where does this data come from - in debs the
data is in the package header afaict - so where do the rpm people
extract it from? Where does apt-rpm store it - b/c then _that_ metadata
file is critical.

-sv