Dependancies of Debian Archive (FYI)
Let's ponder about a question of "How important is a package?"
One measure is "how many other packages depend on it?"
I did some quick(*) research(**) on the Debian archive (stable, testing,
unstable combined) and found out followings:
12% of packages had dependencies with more than 5 other packages
88% of packages had dependencies with less than 6 other packages
24% of packages had dependencies with more than 1 other packages
76% of packages had dependencies with one other package or none
As you can see, most (>75%-90%) packages have very limited impact to
the archive consistency. (I know impact of Build-dep also needs be
assessed but its effects should also be very limited too.)
Currently, minor release does not allow any upstream version bumping but
just security bug fixes. I wonder that is the right approach or not for
these *less* important packages.
Just a note to remind well known facts in quantitative manner :-) Kinda
(*) It was more than 1 hour on 2GHz machine.
Multi-level dependencies were considered.
(**) The full list is at http://people.debian.org/~osamu/pub/rev-stat.321
Top winners are:
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +++++
Osamu Aoki <email@example.com> Cupertino CA USA, GPG-key: A8061F32
.''`. Debian Reference: post-installation user's guide for non-developers
: :' : http://qref.sf.net and http://people.debian.org/~osamu
`. `' "Our Priorities are Our Users and Free Software" --- Social Contract