I can see strong arguments for making C6PAN a database for the reasons you give.

/perl/lib on the other hand - please no! Reasons:

• At the moment, if an error occurs in a module as a result of me passing a duff parameter, making a mistake in syntax etc, I type  vi, cut and paste the filename from the error message, and see the code straight away. Putting it into a database would significantly increase the overhead of that (start database client, spool to file, query, exit, read file....)
• Having some sort of database dependency (apart from potential cross platform problems) would potentially increase the footprint of a perl installation - which would present yet another obstacle to perl on small devices like PDAs.