Data-Reuse 0.13 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/Data-Reuse-0.13,PaxHeader/Data-Reuse-0.13,Data-Reuse-0.13/PaxHeader/CHANGELOG,Data-Reuse-0.13/PaxHeader/CHANGELOG,Data-Reuse-0.13/PaxHeader/MANIFEST,Data-Reuse-0.13/PaxHeader/MANIFEST,Data-Reuse-0.13/PaxHeader/ppport.h,Data-Reuse-0.13/PaxHeader/ppport.h,Data-Reuse-0.13/PaxHeader/t,Data-Reuse-0.13/PaxHeader/t,Data-Reuse-0.13/PaxHeader/README,Data-Reuse-0.13/PaxHeader/README,Data-Reuse-0.13/PaxHeader/META.yml,Data-Reuse-0.13/PaxHeader/META.yml,Data-Reuse-0.13/PaxHeader/lib,Data-Reuse-0.13/PaxHeader/lib,Data-Reuse-0.13/PaxHeader/Makefile.PL,Data-Reuse-0.13/PaxHeader/Makefile.PL,Data-Reuse-0.13/PaxHeader/META.json,Data-Reuse-0.13/PaxHeader/META.json,Data-Reuse-0.13/lib/PaxHeader/Data,Data-Reuse-0.13/lib/PaxHeader/Data,Data-Reuse-0.13/lib/Data/PaxHeader/Reuse.pm,Data-Reuse-0.13/lib/Data/PaxHeader/Reuse.pm,Data-Reuse-0.13/t/PaxHeader/10fixate.t,Data-Reuse-0.13/t/PaxHeader/10fixate.t,Data-Reuse-0.13/t/PaxHeader/30forget.t,Data-Reuse-0.13/t/PaxHeader/30forget.t,Data-Reuse-0.13/t/PaxHeader/20spread.t,Data-Reuse-0.13/t/PaxHeader/20spread.t,Data-Reuse-0.13/t/PaxHeader/00reuse.t,Data-Reuse-0.13/t/PaxHeader/00reuse.t
- 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.
- 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 |
---|---|---|---|
Data::Reuse | share constant values with Data::Alias | 0.13 | metacpan |