I like it.

I don't know if you're aware of Module::MetaInfo, so i'd like to quote from it:

This module is designed to provide the primary interface to Perl meta information for perl module distribution files (this, however, is a prototype and hasn't yet been accepted by the "perl community", so don't count on it yet). The module is designed to allow perl modules to be easily and accurately packaged by other package systems such as RPM and DPKG.

The Module::MetaInfo module isn't actually designed to get any meta information from the perl module. Instead it serves as an entry point to other modules which have their own way of doing that. Since there isn't yet any agreed way to store meta-information in perl modules this may not be very reliable.

Currently there are two ways of getting meta information: a) guessing from the contents of the module and b) using a directory structure which has not yet been accepted by the perl community. The default way this module works is to first try b) then try a) then to give up.

I'm all for this idea.

The CPAN community has been very friendly, but it has also been very loose.

We need official community accepted/defined standards.

You can depend on ExtUtils::MakeMaker for installing perl modules, well that's not where it should stop.

A Module::Signature is also a good idea.

I use Module::ScanDeps MJD says you can't just make shit up and expect the computer to know what you mean, retardo! ** The Third rule of perl club is a statement of fact: pod is sexy.