> > you can do all sorts of things to pre-empt them by using include/exclude > > lists but it's not the same thing as having a 'trump-card repo' > > But maintaining include/exclude lists is also hard when you are pointing > to "arbitrary" repositories. It is not practical to scan the repositories > and build include/exclude lists to add the functionality that was removed. I don't disagree. But repository scoring as a super-epoch to trump versions of packages that are higher seem like the wrong solution to me. -sv
