Kwalitee Issues

has_meta_yml

Add a META.yml to the distribution. Your buildtool should be able to autogenerate it.

has_human_readable_license

Add a section called "LICENSE" to the documentation, or add a file named LICENSE to the distribution.

has_license_in_source_file

Add =head1 LICENSE and the text of the license to the main module in your code.

manifest_matches_dist

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.

Error: Cannot find MANIFEST in dist.

prereq_matches_use

List all used modules in META.yml requires

Error:

  • Archive::Tar
  • HTTP::Request::Common
  • LWP::UserAgent
  • URI::URL

main_module_version_matches_dist_version

Make sure that the main module name and version are the same of the distribution.

no_pod_errors

Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.

Error: releasesystem/IMS-ReleaseMgr/ReleaseMgr/Utils.pm -- Around line 1540: You forgot a '=back' before '=head1' releasesystem/devmgr/man4/dev_release.cfg.pod -- Around line 32: You forgot a '=back' before '=head1'

has_meta_json

Add a META.json to the distribution. Your buildtool should be able to autogenerate it.

proper_libs

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: IMS-ReleaseMgr/ReleaseMgr.pm, IMS-ReleaseMgr/ReleaseMgr/Access.pm, IMS-ReleaseMgr/ReleaseMgr/FileList.pm, IMS-ReleaseMgr/ReleaseMgr/Signature.pm, IMS-ReleaseMgr/ReleaseMgr/Transfer.pm, IMS-ReleaseMgr/ReleaseMgr/Utils.pm

meta_yml_has_license

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.

has_known_license_in_source_file

Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.

use_warnings

Add 'use warnings' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.

Error: IMS::ReleaseMgr, IMS::ReleaseMgr::Access, IMS::ReleaseMgr::FileList, IMS::ReleaseMgr::Signature, IMS::ReleaseMgr::Transfer, IMS::ReleaseMgr::Utils

consistent_version

Split the distribution, or fix the version numbers to make them consistent (use the highest version number to avoid version downgrade).

Error: 1.02,1.03,1.12,1.19

has_separate_license_file

This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.

configure_prereq_matches_use

List all modules used in the Makefile.PL/Build.PL in META.yml configure_requires

Error:

  • Archive::Tar
  • LWP

Modules

Name Abstract Version View
IMS::ReleaseMgr Perl extension for managing IMS Release Manager packages 1.12 metacpan
IMS::ReleaseMgr::Access A small module to abstract the Access Control Lists 1.03 metacpan
IMS::ReleaseMgr::FileList Create a simple IMS-compatible upload package. 1.02 metacpan
IMS::ReleaseMgr::Signature Generate checksums (signatures) 1.03 metacpan
IMS::ReleaseMgr::Transfer Encapsulate physical transport of packages. 1.12 metacpan
IMS::ReleaseMgr::Utils A collection of utility routines for rlsmgr scripts 1.19 metacpan

Other Files

IMS-ReleaseMgr/MANIFEST metacpan
IMS-ReleaseMgr/Makefile.PL metacpan
README metacpan
devmgr/Makefile.PL metacpan
rlsmgr/MANIFEST metacpan
rlsmgr/Makefile.PL metacpan