I wrote: > Salve J Nilsen wrote: > > Bug #4: There isn't a sufficiently clear test output summary telling > > Joe 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? > That would be very useful, both for non-perl people installing stuff, > and also for authors
David Golden thought that this might be more useful as a web thing than done by email by the CPAN testers, so I hacked something up: http://cpandeps.cantrell.org.uk/ It's a foul, disgusting hack. If anyone wants to make it less sucky (eg to work off local databases of test results instead of just naively web-scraping) then the source is available too. Try it with something like Catalyst to see the test results for half of the CPAN. -- David Cantrell | Official London Perl Mongers Bad Influence There once a a tramp with "enable" Whose router used proprietary cables. When he got pissed on meths, He thought "screw IOS", "Let's apt-get install iptables"
