VIM-Packager 0.01 Deleted
Kwalitee Issues
- 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: cpan.vim - has_abstract_in_pod
-
Provide a short description in the NAME section of the pod (after the module name followed by a hyphen) at least for the main module of this distribution.
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: VIM-Packager-0.01/lib/VIM/Packager/Command/Init.pm -- Around line 20: Unknown directive: =name Around line 22: Unknown directive: =author Around line 28: Unknown directive: =type Around line 30: Unknown directive: =dependency Around line 38: Unknown directive: =script Around line 42: Unknown directive: =repository
- 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: VIM::Packager::Manifest - no_invalid_versions
-
Fix the version numbers so that version::is_lax($version) returns true.
Error:- lib/VIM/Packager/MakeMaker.pm: HASH(0x56553aa2bbb0)
- 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.01,0.1
- 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.
Modules
| Name | Abstract | Version | View |
|---|---|---|---|
| VIM::Packager | 0.01 | metacpan | |
| VIM::Packager::Command | metacpan | ||
| VIM::Packager::Command::Build | metacpan | ||
| VIM::Packager::Command::Init | metacpan | ||
| VIM::Packager::Installer | metacpan | ||
| VIM::Packager::MakeMaker | metacpan | ||
| VIM::Packager::Manifest | 0.1 | metacpan | |
| VIM::Packager::MetaReader | metacpan | ||
| VIM::Packager::MetaWriter | metacpan | ||
| VIM::Packager::Utils | metacpan |
Other Files
| Changes | metacpan |
| MANIFEST | metacpan |
| META.yml | metacpan |
| Makefile.PL | metacpan |
| README.mkd | metacpan |