Am 19.01.2011 13:32, schrieb Seblu: >> If package A depends on package B, and B depends on C, then A might >> depend on C explicitly because it accesses C directly. Or it might only >> depend on indirectly C because B accesses C. We should reflect that in >> dependencies (in the first case, A depends on C, in the second case it >> doesn't). >> >> The result is this: Whenever the dependencies of B change (e.g., C is >> removed), A will still work correctly. > > And this check is done by a software not by a "scientist" predicate > that varies depending on the experience of maintainer.
For library-dependencies on binaries, yes. On scripts it is much harder to check this. I don't think it is possible to cover all cases with a piece of software here, but one should try.
signature.asc
Description: OpenPGP digital signature
