showing dependency trees

[Jeff Spaleta]

2009/8/24 Björn Persson <bjorn at xn--rombobjrn-67a.se>:
> One likely cause is that package C, somewhere in the dependency chain between
> A and E, contains too many different functions. In that case C should probably
> be split into subpackages C1 and C2, where C1 depends on A but E depends on
> C2. Then E would no longer depend on A.

I hope you understand that chasing down every single instance of this
situation ultimately leads to a situation that is more easily
duplicated by making the build process automatically split every
library binary into its own subpackage.  If we aren't willing to do
that automatically, then why is it worth the time to have multiple
individuals systematically chase them down?  I'm wary that the sort of
checking you want to do is a rabbit hole that will require significant
continued human effort as codebases shift.

-jef