On Tue, 2010-12-21 at 00:52 +0100, Henrik NordstrÃm wrote: > mÃn 2010-12-20 klockan 16:15 -0500 skrev seth vidal: > > > So you want to give updates-testing preferential value over updates > > despite their being no e-v-r difference between the pkgs? If so - you > > can do that now with yum's cost value. > > No. The stable repositories (updates / dist) always have priority over > testing. > > Better to explain with example I think. > > Repository contents: > > updates: foo-1.0.54 > updates-testing: foo-1.1.1 > > BuildRequires: foo > > uses foo-1.0.54 as that's the latest stable release, as usual. > > BuildRequires: foo >= 1.1 > > uses foo-1.1.1 from updates-testing as that's the best match for > satisfying the requirement even if that release is not yet pushed as > stable. > > > If the dependency still can not be resolved when including > updates-testing then it's a failed dependency. No change suggested in > e-v-r matching criterias, only dependency resolution in which > repositories to query when. > > > could be implemented by using updates-testing as fallback package > repository queried only on packages which could not get resolved from > the normal enabled repositories (i.e. dist & updates) Have you looked at the yum config mock uses? And how yum resolves deps when multiple pkgs provide the same requirement? http://yum.baseurl.org/wiki/CompareProviders -sv -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
