setupsup 1.0.1.0 Latest
Kwalitee Issues
- extracts_nicely
-
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: mswin32-x86-multi-thread;setupsup.316.pll;setupsup.522.dll;main.cpp;resource.rc;wstring.cpp;makefile;setupsup.h;setupsup.cpp;setupsup.615.dll;wstring.h;history.txt;plmisc.cpp;win32-setupsup.ppd;usererror.h;x86;setupsup.pm;setupsup.def;install.pl;restrict.txt;list.cpp;misc.h;list.h;plmisc.h;resource.h;misc.cpp
- has_readme
-
Add a README to the distribution. It should contain a quick description of your module and how to install it.
- has_manifest
-
Add a MANIFEST to the distribution. Your buildtool should be able to autogenerate it (eg "make manifest" or "./Build manifest")
- has_meta_yml
-
Add a META.yml to the distribution. Your buildtool should be able to autogenerate it.
- has_buildtool
-
Add a Makefile.PL (for ExtUtils::MakeMaker/Module::Install) or a Build.PL (for Module::Build and its friends), or use a distribution builder such as Dist::Zilla, Dist::Milla, Minilla.
- has_tests
-
Add tests!
- 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.
- 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: Cannot find MANIFEST in dist.
- use_strict
-
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.
Error: Win32::Setupsup
- prereq_matches_use
-
List all used modules in META.yml requires
Error:
- Win32::Registry
- 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: setupsup.pm -- Around line 693: You forgot a '=back' before '=head1'
- has_meta_json
-
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
- has_tests_in_t_dir
-
Add tests or move tests.pl to the t/ directory!
- 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.
- 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.
- 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: Win32::Setupsup
- has_separate_license_file
-
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.
Modules
Name | Abstract | Version | View |
---|---|---|---|
Win32::Setupsup | implements some functions to automate setups which have no silent mode | metacpan |