On Tue, 5 Feb 2008, Jason Corley wrote:

>    - integrated depsolver

The issue there, as I see it, is what (existing, additional, 
new <?>) mechanisms will be devised to specify 'target 
repositories' to consider in doing the dep-solveing.  A whole 
set of structures in the yum space have emerged, to specify 
candidate repositories to use (along with some lily gilding 
about excludes, and priorities.)  Also the format has been 
tweaked with some changes occasionally.

No reason not to accept the hint (pointer) to the top of 
archives, as per 'createrepo' as that has become familiar, but 
should one suck in the metadata, or pull it off the observed 
binary RPM's found?  Debian solved it another way -- should 
RPM 'grok' /etc/apt/sources.list as well?

What other archive identification mechanisms are out there 
which need to be considered which I have missed? BSD ports 
pointers? HP Depot pointers ;) ?

-- Russ herrold