On Sun, Sep 1, 2019 at 1:15 PM Drew Parsons <dpars...@debian.org> wrote: > It could be useful to add another column counting the Dependencies in > the other direction. > > i.e. for all the leaf packages ready for processing, which one should be > given priority? Which one has the most impact on Dependencies further > down the tree?
I'm afraid i dont understand the question, or maybe it's just a different process than the one i use. the main idea (behind the webpage) is that you cant remove a package unless it doesnt have any reverse-dependency: so if the count it's 0, you can go ahead and remove it. if it has rdeps, then you need to address them _first-, and that's where the rdeps graph comes handy, as it tells you the actual packages. but what i personally use is a level 4 graph (so up to 4 levels of reverse depends): say you want to work on pkgA, but it turns out it has some rdeps, pkg0..8; now, how many rdeps does each of these packages have? hard to say with only a level=1 graph, as you dont see further in the deps tree (the risk it get crazy pretty quickly, in particular with sci packages, as currently all debian-science tasks packages depend on the py2 pkgs, if one of them gets pulled in it's hard to read). Let me know if i can make the webpage more useful for you, i just dont know how to address your request -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
