Class-Tangram 1.57 Latest
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.
Upgrade the bundled version of Module::Install to the most current release. Alternatively, you can switch to another build system / installer that does not suffer from this problem. (ExtUtils::MakeMaker, Module::Build both of which have their own set of problems.)
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: Class-Tangram-1.57/lib/Class/Tangram.pm -- Around line 396: You can't have =items (as at line 405) unless the first thing after the =over is an =itemAround line 2940: Non-ASCII character seen before =encoding in 'ï¿½Â©'. Assuming CP1252
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.
Split the distribution, or fix the version numbers to make them consistent (use the highest version number to avoid version downgrade).
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.
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.
Error: Class::Tangram, Class::Tangram::Generator, Class::Tangram::Generator::Stub
List all modules used in the test suite in META.yml build_requires
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.
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.
Add a 'repository' resource to the META.yml via 'meta_add' accessor (for Module::Build) or META_ADD parameter (for ExtUtils::MakeMaker).