Kwalitee Issues

has_changelog

Add a Changelog (best named 'Changes') to the distribution. It should list at least major changes implemented in newer versions.

has_license_in_source_file

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

has_meta_yml

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

main_module_version_matches_dist_version

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

no_files_to_be_skipped

Fix MANIFEST.SKIP or use an authoring tool which respects MANIFEST.SKIP. Note that each entry in MANIFEST.SKIP is a regular expression. You may need to add appropriate meta characters not to ignore necessary stuff.

Error: MANIFEST.SKIP,readme.texi

no_pod_errors

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

Error: Verilog-Perl-1.9/Language .pm -- Around line 49: You forgot a '=back' before '=head1' Around line 56: '=item' outside of any '=over' Around line 60: You forgot a '=back' before '=head1' Around line 67: '=item' outside of any '=over' Around line 73: You forgot a '=back' before '=head1' Around line 80: '=item' outside of any '=over' Around line 85: You forgot a '=back' before '=head1' Around line 90: '=item' outside of any '=over'

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.4,1.5,1.9

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.

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!

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.

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: Language.pm, Parse.pm, Parser.pm, SigParser.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: Verilog::Language, Verilog::Parse, Verilog::Parser, Verilog::SigParser

Modules

Name Abstract Version View
Verilog::Language Verilog language utilities 1.9 metacpan
Verilog::Parse parse Verilog language files 1.4 metacpan
Verilog::Parser Parse Verilog language files 1.9 metacpan
Verilog::SigParser Signal Parsing for Verilog language files 1.5 metacpan

Other Files

MANIFEST metacpan
Makefile.PL metacpan
README metacpan