[PATCH setup 00/14] Use libsolv, solve all our problems... (WIP)

Achim Gratz Stromeko@nexgo.de
Thu Nov 23 20:54:00 GMT 2017

Jon Turney writes:
>>> You can give each repo a priority and it will pick the package from the
>>> one with the highest priority, even if another repo has a higher
>>> version.
>> Yes, that works.
> It seems that, when test versions are enabled, a test version is
> preferred over a non-test version with a higher version
> I guess this is a consequence of:
>> void
>> SolverPool::use_test_packages(bool use_test_packages)
>> {
>>   // Give repos containing test packages higher priority than normal
>>   // if wanted, otherwise lower priority.
>>   SolvRepo::priority_t p = use_test_packages ? SolvRepo::priorityHigh : SolvRepo::priorityLow;
> I wonder if we just want to give test repos priorityNormal when they
> are wanted?

It really depends on what you are trying to achieve (and assuming you always
work on all enabled repositories instead of specifically selecting one).

1) To chose the highest version available among a set of repositories
(these need to be compatible in their versioning), then the priorities
of all those repos need to be the same.

2) To prefer one repo over the other regardless of versioning
(versioning need not be compatible), then raise the priority of the
preferred repo.

We currently can't use the difference between an update and
distribution upgrade in setup since we would have to record which repo
each package was originally installed from.  If we had that, an update
would keep the repository selection (even if another repo has a higher
version) and a distribution upgrade would select the highest version,
switching repositories as necessary.

+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:

More information about the Cygwin-apps mailing list