Terse-Static 0.07
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: Terse-Static-0.07/PaxHeader/Changes,Terse-Static-0.07/PaxHeader/Changes,Terse-Static-0.07/PaxHeader/ignore.txt,Terse-Static-0.07/PaxHeader/ignore.txt,Terse-Static-0.07/PaxHeader/README,Terse-Static-0.07/PaxHeader/README,Terse-Static-0.07/PaxHeader/Makefile.PL,Terse-Static-0.07/PaxHeader/Makefile.PL,Terse-Static-0.07/lib/Terse/PaxHeader/Static.pm,Terse-Static-0.07/lib/Terse/PaxHeader/Static.pm,Terse-Static-0.07/lib/Terse/View/PaxHeader/Static.pm,Terse-Static-0.07/lib/Terse/View/PaxHeader/Static.pm,Terse-Static-0.07/lib/Terse/View/Static/PaxHeader/Memory.pm,Terse-Static-0.07/lib/Terse/View/Static/PaxHeader/Memory.pm,Terse-Static-0.07/lib/Terse/Controller/PaxHeader/Static.pm,Terse-Static-0.07/lib/Terse/Controller/PaxHeader/Static.pm,Terse-Static-0.07/xt/PaxHeader/boilerplate.t,Terse-Static-0.07/xt/PaxHeader/boilerplate.t,Terse-Static-0.07/t/PaxHeader/pod.t,Terse-Static-0.07/t/PaxHeader/pod.t,Terse-Static-0.07/t/PaxHeader/manifest.t,Terse-Static-0.07/t/PaxHeader/manifest.t,Terse-Static-0.07/t/PaxHeader/00-load.t,Terse-Static-0.07/t/PaxHeader/00-load.t,Terse-Static-0.07/t/PaxHeader/pod-coverage.t,Terse-Static-0.07/t/PaxHeader/pod-coverage.t
- use_strict
-
Add 'use strict' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules are strictly written.
Error: Terse::Controller::Static, Terse::Static, Terse::View::Static, Terse::View::Static::Memory
- 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: Terse::Controller::Static, Terse::Static, Terse::View::Static, Terse::View::Static::Memory
- 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.