[Yum-devel] requested 'protectbase', as used in yum 2.0

seth vidal skvidal at phy.duke.edu
Mon Mar 7 03:46:18 UTC 2005


> the repo scoring implementation code-wise is not all that hard - you
> just add an attribute to the repository object and you use that as your
> first-order separation when you have two packages of the same name from
> different repositories providing the same requirement.
> 
> Of course this doesn't even get into how you deal with obsoletes. Can a
> package from a score 0 repo obsolete a score 2? 

one other odd point:

rpmdb: foo-1.1-1
repo1(score 0) foo-1.1-10
repo2(score 20) foo-1.1-2

command: yum update foo

now, by scoring you'd get:
foo-1.1-2 updating over foo-1.1-1
 b/c repo2's score is 20 and repo1's score is 0

so we complete that function and we end up with:
rpmdb: foo-1.1-2
repo1 (score 0) foo-1.1-10
repo2 (score 20) foo-1.1-2 

but we have no way of knowing the repo score of the installed package,
nor any way of decisively knowing what repo it came from. Won't we end
up with foo-1.1-10 updating overtop of foo-1.1-2 in the rpmdb?

It seems like if we're going to have an additional number determining
dependency resolution then we should continue to have that information
in the rpmdb.

-sv





More information about the Yum-devel mailing list