Apache-PerlVINC 0.03 Latest
Add a Changelog (best named 'Changes') to the distribution. It should list at least major changes implemented in newer versions.
Add a META.yml to the distribution. Your buildtool should be able to autogenerate it.
Add a README to the distribution. It should contain a quick description of your module and how to install it.
Run a proper command ("make manifest" or "./Build manifest", maybe with a force option), or use a distribution builder to generate the MANIFEST. Or update MANIFEST manually.
- MANIFEST (3) does not match dist (4):
- Missing in MANIFEST: INSTALL
List all used modules in META.yml requires
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
Add tests or move tests.pl to the t/ directory!
Define the license if you are using in Build.PL. If you are using MakeMaker (Makefile.PL) you should upgrade to ExtUtils::MakeMaker version 6.31.
Move your *.pm files in a directory named 'lib'. The directory structure should look like 'lib/Your/Module.pm' for a module named 'Your::Module'. If you need to provide additional files, e.g. for testing, that should not be considered for Kwalitee, then you should look at the 'provides' map in META.yml to limit the files scanned; or use the 'no_index' map to exclude parts of the distribution.
Error: PerlVINC.pm, PerlVINC.pm
Add 'use warnings' (or its equivalents) to all modules (this will require perl > 5.6), or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.
|Apache::PerlVINC||Allows versioning of modules among directories or v-hosts.||0.03||metacpan|