Re: Architecture support

> In apt, you can set up repositories such that the reference in 
> sources.list is not architecture-specific.  This is possible because apt 
> does some interpretation of the fields in sources.list and builds URIs 
> from them using a standard algorithm.
> 
> Obviously, such a scheme can't be built into the rpm-metadata stuff. 
> But we could allow for an architecture attribute on the metadata node, 
> something like this:
> 
> <metadata arch="i386">
>    <data type="primary"/>
>    <data type="filelist"/>
>    <data type="other"/>
>    <data type="groups"/>
> </metadata>
> <metadata arch="powerpc">
>    <data type="primary"/>
>    <data type="filelist"/>
>    <data type="other"/>
>    <data type="groups"/>
> </metadata>
> 
> The attribute could be optional, in which case it's assumed that the 
> repository is correct.
> 
> What does everyone think of this?

I'm troubled by it b/c what if you have a repository that has files for
LOTS of archs and you want the client tool to sort out which ones it
should want

for example, the fedora development tree(formerly known as rawhide) has
one big repo for ALL archs.

Can you explain how that should be handled? 

Thanks
-sv