diff options
author | David Kalnischkies <david@kalnischkies.de> | 2022-09-02 11:07:58 +0200 |
---|---|---|
committer | David Kalnischkies <david@kalnischkies.de> | 2022-09-02 23:37:58 +0200 |
commit | e1f332324f81b589561a9d9bce8a55d4895f26ec (patch) | |
tree | f70554096438ee2c629ad1a515f34c5d92e0cb89 /CMake | |
parent | 009cf61122b7a0ac22b541035a26e6092c9ac529 (diff) |
Respect users pkg order on `apt install` for resolving
The command line is evaluated in two steps: First all packages given
are marked for install and as a second step the resolver is started on
all of them in turn to get their dependencies installed.
This is done so a user can provide a non-default choice on the command
line and have it respected regardless of where on the command line it
appears.
On the other hand, the order in which dependencies are resolved can
matter, so instead of using a "random" order, we now do this in the
order given on the command line, so if you e.g. have a meta package
pulling in non-default choices and mention it first the choices are
respected predictably instead of depending on first appearance of the
package name while creating the binary cache.
I might have "broken" this more than a decade ago while introducing the
reworked command line parsing for Multi-Arch, which also brought in the
split into the two steps mentioned above which was the far more
impactful 'respect user choice' change. This one should hardly matter in
practice, but as the tests show, order can have surprising side effects.
Diffstat (limited to 'CMake')
0 files changed, 0 insertions, 0 deletions