Tk-Markdown 0.01 Deleted
Kwalitee Issues
- has_meta_yml
-
Add a META.yml to the distribution. Your buildtool should be able to autogenerate it.
- no_generated_files
-
Remove the offending files/directories!
Error: Makefile, pm_to_blib
- no_mymeta_files
-
Update MANIFEST.SKIP to exclude MYMETA files. If you are lazy, add "#!install_default" in your MANIFEST.SKIP and update your ExtUtils::Manifest if necessary, then some of the most common files will be excluded.
- manifest_matches_dist
-
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.
Error:
- MANIFEST (9) does not match dist (25):
- Missing in MANIFEST: MYMETA.json, MYMETA.yml, Makefile, blib/arch/.exists, blib/arch/auto/Tk/Markdown/.exists, blib/bin/.exists, blib/html/site/lib/Tk/Markdown.html, blib/lib/Tk/.exists, blib/lib/Tk/Markdown.pm, blib/lib/auto/Tk/Markdown/.exists, blib/man1/.exists, blib/man3/.exists, blib/script/.exists, ignore.txt, pm_to_blib, t/boilerplate.t
- prereq_matches_use
-
List all used modules in META.yml requires
Error:
- Tk::Derived
- Tk::Font
- Tk::Text
- main_module_version_matches_dist_version
-
Make sure that the main module name and version are the same of the distribution.
- has_meta_json
-
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
- proper_libs
-
Move your *.pm files in a directory named 'lib'. The directory structure should look like 'lib/Your/Module.pm' for a module named 'Your::Module'. If you need to provide additional files, e.g. for testing, that should not be considered for Kwalitee, then you should look at the 'provides' map in META.yml to limit the files scanned; or use the 'no_index' map to exclude parts of the distribution.
Error: blib/lib/Tk/Markdown.pm
- 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.
- 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.