This metric attached to each source package A, the number of source packages which need A to be compilable to become compilable themselves in a bootstrapping scenario. So this metric can answer the question: how many source packages are blocked by this source package not being compilable.
To enhance this metric, data from popcon.debian.org is used. This allows to answer the question: what is the sum of popcon values of all source packages blocked by this source package not being compilable.
Since installation sets are not unique, for both of these numbers we give a minimum and a maximum value. The minimum value corresponds to the value calculated from a strong dependency graph (the minimum amount of dependencies between source packages). The maximum value corresponds to the value calculated from a closure graph (the maximum amount of dependencies between source packages).
The data is presented in five columns. The first column is the source package name, the second column the minimum number of source packages blocked by this source package, the third column the maximum number of source packages blocked by this source package, the fourth column the minimum sum of popcon values of the blocked source packages and the fifth column the maximum sum of popcon values: importance_metric_all.txt
In a bootstrapping scenario it can be assumed that all packages that are Essential:yes, build-essential and Architecture:all have been cross compiled and do not need to be re-compiled. The following dataset takes this into account: importance_metric_noall.txt
The data used to generate this page was computed using botch, the bootstrap/build ordering tool chain. The source code of botch can be redistributed under the terms of the LGPL3+ with an OCaml linking exception. The source code can be retrieved from https://gitlab.mister-muffin.de/debian-bootstrap/botch
The html page was generated by code which can be retrieved from https://gitlab.mister-muffin.de/josch/boott and which can be redistributed under the terms of the AGPL3+
For questions and bugreports please contact j [dot] schauer [at] email [dot] de.