The YAPC talk about Plagger was very interesting so I tried installing it.
The talk said installing Plagger was a challenge and so it proved. A couple of dozen dozen modules were required from CPAN, to make things worse I decided to install all the optional modules and tried to install on a machine I do not have root on. Things went kinda bad,lots of stuff needed paths for libs I did not have installed and header files that were no where to be seen,tests failed and due to some recent changes on redbrick cpan ended up mixing sparc and intel shared libs up together. I'll try again tomorrow on a machine I have root on, where the directories are used only by one architecture and choose less optional modules. Things can only get better.
Since my local install area was all messed up I cleaned it out, fixed my cpan config so it doesn't mix different arch shared libs up and started installing the modules I need for some local programs and a few small webaps of mine that other people use on a daily basis. This is where stuff gets a little annoying, applying tiny but important fixes to modules or ignoring failing tests and hoping they do not matter. Some of these have already had fixes accepted by the author but no subsequent cpan release have ever taken place, some the author has fallen off the side of the internet and no one has jumped in to take their place. If only there was some way we could quantify author awakiness, perform some loving restoration on important/unique/very useful modules that need it or bias search away from dead ends that have better more alive alternatives. The first half probably exists informally but the second sounds tough without some quantitative support infrastructure.