A recent thread on perl-qa threw up an interesting idea: Salve J Nilsen wrote:
> There isn't a sufficiently clear test output summary telling > [the user] which module broke the dependency chain - so he can't look > into it himself. Visualizing the dependencies and show where it broke > may help. Maybe displaying the relevant dependencies in a way like > tree(1) does? It's certainly an interesting idea. Right now we ignore test failures when a pre-requisite is missing, but putting my module author hat on, I think I really would like to know that my module couldn't be installed on some random platform because the latest version of one of my dependencies is broken. It would let me either find an alternative dependency, eliminate the dependency if I can trivially code around it, or help the other author fix his bug. Thoughts? -- David Cantrell | Nth greatest programmer in the world What profiteth a man, if he win a flame war, yet lose his cool?
