XS-MRO-Compat 0.10 Deleted
Kwalitee Issues
- meta_yml_conforms_to_known_spec
-
Take a look at the META.yml Spec at https://metacpan.org/pod/CPAN::Meta::History::Meta_1_4 (for version 1.4) or https://metacpan.org/pod/CPAN::Meta::Spec (for version 2), and change your META.yml accordingly.
Error: Key 'mro_compat.h' is not a legal module name. (provides -> mro_compat.h) [Validation: 1.4]
- has_abstract_in_pod
-
Provide a short description in the NAME section of the pod (after the module name followed by a hyphen) at least for the main module of this distribution.
- 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: ./mro_compat.h
- no_missing_files_in_provides
-
Use authoring tool like Dist::Zilla, Milla, and Minilla to generate correct provides.
Error: ./mro_compat.h
- has_separate_license_file
-
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.