That should fix the case where we update JSON::Tiny for example (which is a panda dependency), and afterwards panda breaks because it was compiled for an older version of JSON::Tiny. After this panda will detect its dependency on JSON::Tiny and rebuild itself.
This is WIP. It will create a test report file once a dist installation is attempted. See this example of a FAIL: https://gist.github.com/FROGGS/5b25776e1ce3f297cb05 Next step is to submit these reports for review to a web service. We also need to ask the user for permission to generate and send these reports.
Not just the first writable one we find. This (for example) allows a (root) install of perl6+panda into /usr/local; along with some modules such as URI and MIME::Base64. A user can then run 'panda install LWP::Simple' and will not need to reinstall URI and MIME::Base64, because panda will now see the modules installed in /usr/local