Term-Sample 0.25 Latest
Pack the distribution with a proper command such as "make dist" and "./Build dist", or use a distribution builder such as Dist::Zilla, Dist::Milla, Minilla.
Error: More than one top directories are found: README;Sample.pm;Changes;Makefile.PL;sample.htm;examples;MANIFEST
Add a section called "LICENSE" to the documentation, or add a file named LICENSE to the distribution.
Add =head1 LICENSE and the text of the license to the main module in your code.
Add a META.yml to the distribution. Your buildtool should be able to autogenerate it.
Fix the version(s).
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.
- MANIFEST (5) does not match dist (11):
- Missing in MANIFEST: README, Sample.pm, examples/passwd.pl, examples/sample.pl, examples/set.pl, examples/spasswd.pl, examples/synopsis.pl, sample.htm
- Missing in Dist: Temp.pm, test.pl
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: Sample.pm -- Around line 898: '=item' outside of any '=over'Around line 1028: You forgot a '=back' before '=head1'Around line 1030: '=item' outside of any '=over'Around line 1072: Unknown directive: =iutemAround line 1110: You forgot a '=back' before '=head1'Around line 1273: '=item' outside of any '=over'Around line 1292: You forgot a '=back' before '=head1'
List all used modules in META.yml requires
Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
Add tests or move tests.pl to the t/ directory!
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.
Add 'use warnings' (or its equivalents) to all modules (this will require perl > 5.6), or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.