metaperl-dbix-dbh-e0cfebd Latest
Kwalitee Issues
- has_version
-
Add a version number to the packed distribution. Or use a buildtool ('make dist' or 'Build dist')
- has_proper_version
-
Remove all letters from the version number. If you want to mark a release as a developer release, use the scheme 'Module-1.00_01'
- distname_matches_name_in_meta
-
Use a proper tool to make a distribution. You might also need to fix META files if you keep them in the repository.
Error: DBIx-DBH
- buildtool_not_executable
-
Change the permissions of Build.PL/Makefile.PL to not-executable.
- no_generated_files
-
Remove the offending files/directories!
Error: Makefile
- 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 (20) does not match dist (22):
- Missing in MANIFEST: .gitignore, Makefile
- 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: DBIx::DBH::Pg, DBIx::DBH::SQLite, DBIx::DBH::Sybase, DBIx::DBH::mysql
- 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: metaperl-dbix-dbh-e0cfebd/lib/DBIx/DBH/Legacy.pm -- Around line 204: You forgot a '=back' before '=head3' Around line 285: =back without =over Around line 339: You forgot a '=back' before '=head1'
- 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.
- has_meta_json
-
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
- 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.
- 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: DBIx::DBH::Pg, DBIx::DBH::SQLite, DBIx::DBH::Sybase, DBIx::DBH::mysql
- 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.2,0.5
- 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.
- has_security_doc
-
Add SECURITY(.pod|md). See Software::Security::Policy.
- security_doc_contains_contact
-
Add SECURITY(.pod|md) and add a contact address. See Software::Security::Policy.
- has_contributing_doc
-
Add CONTRIBUTING(.pod|md). See https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.