Yote 0.03 Deleted
Kwalitee Issues
- has_meta_yml
-
Add a META.yml to the distribution. Your buildtool should be able to autogenerate it.
- has_changelog
-
Add a Changelog (best named 'Changes') to the distribution. It should list at least major changes implemented in newer versions.
- buildtool_not_executable
-
Change the permissions of Build.PL/Makefile.PL to not-executable.
- no_generated_files
-
Remove the offending files/directories!
Error: Build
- 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 (37) does not match dist (51):
- Missing in MANIFEST: Build, MYMETA.yml, _build/auto_features, _build/build_params, _build/cleanup, _build/config_data, _build/features, _build/magicnum, _build/notes, _build/prereqs, _build/runtime_params, emacs-X11.exe.stackdump, install, lib/Yote/emacs-X11.exe.stackdump
- prereq_matches_use
-
List all used modules in META.yml requires
Error:
- DBI
- feature
- main_module_version_matches_dist_version
-
Make sure that the main module name and version are the same of the distribution.
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: Yote/lib/Yote/ClientObj.pm -- Around line 32: Unknown directive: =NAME Around line 36: Unknown directive: =SYNOPSIS
- 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_meta_json
-
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
- use_warnings
-
Add 'use warnings' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.
Error: Yote::AppRoot, Yote::Array, Yote::ClientObj, Yote::Hash, Yote::MysqlIO, Yote::Obj, Yote::ObjProvider, Yote::SQLiteIO, Yote::Test::Hello, Yote::Test::TestAppNeedsLogin, Yote::Test::TestAppNoLogin, Yote::WebAppServer
- test_prereq_matches_use
-
List all modules used in the test suite in META.yml test_requires
Error:
- Test::Pod
- 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.
- configure_prereq_matches_use
-
List all modules used in the Makefile.PL/Build.PL in META.yml configure_requires
Error:
- Module::Build
Modules
Name | Abstract | Version | View |
---|---|---|---|
Yote::AppRoot | Application Server Base Objects | 0.01 | metacpan |
Yote::Array | All arrays in the Yote system get tied to this class. | 0.01 | metacpan |
Yote::ClientObj | 0.01 | metacpan | |
Yote::Hash | All hashes in the Yote system get tied to this class. | 0.01 | metacpan |
Yote::MysqlIO | A mysql persistance engine for Yote. | 0.01 | metacpan |
Yote::Obj | Base class for all persistant Yote objects. | 0.01 | metacpan |
Yote::ObjProvider | Serves Yote objects. Configured to a persistance engine. | 0.01 | metacpan |
Yote::SQLiteIO | A SQLite persistance engine for Yote. | 0.01 | metacpan |
Yote::Test::Hello | 0.01 | metacpan | |
Yote::Test::TestAppNeedsLogin | 0.01 | metacpan | |
Yote::Test::TestAppNoLogin | 0.01 | metacpan | |
Yote::WebAppServer | is a library used for creating prototype applications for the web. | 0.01 | metacpan |