"Steve M. Robbins" <[email protected]> writes: > This is due to Debian Policy 2.5:
> Packages must not depend on packages with lower priority values > (excluding build-time dependencies). In order to ensure this, the > priorities of one or more packages may need to be adjusted. > Why is this the policy? Why does it matter? Surely installing all > the "important" packages will pull in their dependencies regardless of > the depended-upon package's priority. Ideally, it would be nice to be able to sort out packages by priority and, from that, build, say, a CD set of only the important and higher packages and know that it's self-contained. In practice, I suspect that we have enough packages with problems here that you have to compute the dependency closure anyway, but insofar as priorities are useful for anything, I think that was the goal. (It's not clear at this point to me whether priorities are really useful for anything.) -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
