James Wilkinson wrote:
Paul Howarth wrote:
There are multiple ways
a package can be a dependency, and this query only reveals one of those
Suppose you have a package A, which "provides" libA.so.1 and also
contains the file /bin/A
rpm -q --whatrequires A
will only show you the packages that have an explicit dependency on A
It won't show you the packages that have a dependency on libA.so.1 or
the file /bin/A
And if C has a dependency on B, which has a dependency on A, but C
itself does not *directly* depend on A, then rpm -q --whatrequires won't
show that, either.
This is what is known as the "key inversion problem". There is
no simple solution for this known.
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!