Char-Latin7 0.99
- Released by
- INA
- Version
- Release Date
- 2014-08-05
- Kwalitee
- 134.38
- Core Kwalitee
- 87.5
- LINKS
Char-Latin7 0.99
Kwalitee Issues
- buildtool_not_executable
-
Change the permissions of Build.PL/Makefile.PL to not-executable.
- 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:
- MANIFEST (196) does not match dist (194):
- Duplicates in MANIFEST: Elatin7.pm, Latin7.pm
- 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: Char::Elatin7, Char::Latin7, Elatin7, Latin7
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: Char-Latin7-0.99/Char/Elatin7.pm -- Around line 2969: =over without closing =back Char-Latin7-0.99/Elatin7.pm -- Around line 2969: =over without closing =back
- has_meta_json
-
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
- has_tests_in_t_dir
-
Add tests or move tests.pl to the t/ directory!
- 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: Char/Elatin7.pm, Char/Latin7.pm, Elatin7.pm, Latin7.pm
- 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: Char::Elatin7, Char::Latin7, Elatin7, Latin7
- 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.