Devel-TrackSIG 0.04 Latest
Kwalitee Issues
- no_pax_headers
-
If you use Mac OS X >= 10.6, use gnu tar (/usr/bin/gnutar) to avoid PAX headers. It's also important to rename (shorten) long file names (>= 100 characters) in the distribution.
Error: PaxHeader/Devel-TrackSIG-0.04,PaxHeader/Devel-TrackSIG-0.04,Devel-TrackSIG-0.04/PaxHeader/Changes,Devel-TrackSIG-0.04/PaxHeader/Changes,Devel-TrackSIG-0.04/PaxHeader/lib,Devel-TrackSIG-0.04/PaxHeader/lib,Devel-TrackSIG-0.04/PaxHeader/Makefile.PL,Devel-TrackSIG-0.04/PaxHeader/Makefile.PL,Devel-TrackSIG-0.04/PaxHeader/MANIFEST,Devel-TrackSIG-0.04/PaxHeader/MANIFEST,Devel-TrackSIG-0.04/PaxHeader/META.json,Devel-TrackSIG-0.04/PaxHeader/META.json,Devel-TrackSIG-0.04/PaxHeader/META.yml,Devel-TrackSIG-0.04/PaxHeader/META.yml,Devel-TrackSIG-0.04/PaxHeader/README,Devel-TrackSIG-0.04/PaxHeader/README,Devel-TrackSIG-0.04/PaxHeader/t,Devel-TrackSIG-0.04/PaxHeader/t,Devel-TrackSIG-0.04/t/PaxHeader/01load.t,Devel-TrackSIG-0.04/t/PaxHeader/01load.t,Devel-TrackSIG-0.04/lib/PaxHeader/Devel,Devel-TrackSIG-0.04/lib/PaxHeader/Devel,Devel-TrackSIG-0.04/lib/Devel/PaxHeader/TrackGlobalScalar.pm,Devel-TrackSIG-0.04/lib/Devel/PaxHeader/TrackGlobalScalar.pm,Devel-TrackSIG-0.04/lib/Devel/PaxHeader/TrackSIG.pm,Devel-TrackSIG-0.04/lib/Devel/PaxHeader/TrackSIG.pm
- meta_yml_declares_perl_version
-
If you are using Build.PL define the {requires}{perl} = VERSION field. If you are using MakeMaker (Makefile.PL) you should upgrade ExtUtils::MakeMaker to 6.48 and use MIN_PERL_VERSION parameter. Perl::MinimumVersion can help you determine which version of Perl your module needs.
- 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.
- consistent_version
-
Split the distribution, or fix the version numbers to make them consistent (use the highest version number to avoid version downgrade).
Error: 0.03,0.04
- meta_yml_has_provides
-
Add all modules contained in this distribution to the META.yml field 'provides'. Module::Build or Dist::Zilla::Plugin::MetaProvides do this automatically for you.
- meta_yml_has_repository_resource
-
Add a 'repository' resource to the META.yml via 'meta_add' accessor (for Module::Build) or META_ADD parameter (for ExtUtils::MakeMaker).
- has_separate_license_file
-
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.