fs-Promises 0.04 Latest
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: PaxHeader/fs-Promises-0.04,PaxHeader/fs-Promises-0.04,fs-Promises-0.04/PaxHeader/MANIFEST,fs-Promises-0.04/PaxHeader/MANIFEST,fs-Promises-0.04/PaxHeader/t,fs-Promises-0.04/PaxHeader/t,fs-Promises-0.04/PaxHeader/META.yml,fs-Promises-0.04/PaxHeader/META.yml,fs-Promises-0.04/PaxHeader/lib,fs-Promises-0.04/PaxHeader/lib,fs-Promises-0.04/PaxHeader/Makefile.PL,fs-Promises-0.04/PaxHeader/Makefile.PL,fs-Promises-0.04/PaxHeader/META.json,fs-Promises-0.04/PaxHeader/META.json,fs-Promises-0.04/lib/PaxHeader/fs,fs-Promises-0.04/lib/PaxHeader/fs,fs-Promises-0.04/lib/fs/PaxHeader/Promises,fs-Promises-0.04/lib/fs/PaxHeader/Promises,fs-Promises-0.04/lib/fs/PaxHeader/Promises.pm,fs-Promises-0.04/lib/fs/PaxHeader/Promises.pm,fs-Promises-0.04/lib/fs/Promises/PaxHeader/Utils.pm,fs-Promises-0.04/lib/fs/Promises/PaxHeader/Utils.pm,fs-Promises-0.04/t/PaxHeader/01-read_file.t,fs-Promises-0.04/t/PaxHeader/01-read_file.t,fs-Promises-0.04/t/PaxHeader/02-stat.t,fs-Promises-0.04/t/PaxHeader/02-stat.t
- has_readme
-
Add a README to the distribution. It should contain a quick description of your module and how to install it.
- has_changelog
-
Add a Changelog (best named 'Changes') to the distribution. It should list at least major changes implemented in newer versions.
- has_human_readable_license
-
Add a section called "LICENSE" to the documentation, or add a file named LICENSE to the distribution.
- has_license_in_source_file
-
Add =head1 LICENSE and the text of the license to the main module in your code.
- 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_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.
- 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.