Gedcom 1.15 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: Expected a map structure from string or file. (requires) [Validation: 1.0]
- 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.
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: Gedcom-1.15/Gedcom/Comparison.pm -- Around line 158: '=end' without a target?
- 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.
- 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: Gedcom, Gedcom::CGI, Gedcom::Comparison, Gedcom::Event, Gedcom::Family, Gedcom::Grammar, Gedcom::Grammar_5_5, Gedcom::Individual, Gedcom::Item, Gedcom::LifeLines, Gedcom::Record
- 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.
Modules
Name | Abstract | Version | View |
---|---|---|---|
Gedcom | a module to manipulate Gedcom genealogy files | 1.15 | metacpan |
Gedcom::CGI | Basic CGI routines for Gedcom.pm | 1.15 | metacpan |
Gedcom::Comparison | a module to compare Gedcom records | 1.15 | metacpan |
Gedcom::Event | a module to manipulate Gedcom events | 1.15 | metacpan |
Gedcom::Family | a module to manipulate Gedcom families | 1.15 | metacpan |
Gedcom::Grammar | a module to manipulate Gedcom grammars | 1.15 | metacpan |
Gedcom::Grammar_5_5 | 1.15 | metacpan | |
Gedcom::Individual | a module to manipulate Gedcom individuals | 1.15 | metacpan |
Gedcom::Item | a base class for Gedcom::Grammar and Gedcom::Record | 1.15 | metacpan |
Gedcom::LifeLines | functions for lines2perl | 1.15 | metacpan |
Gedcom::Record | a module to manipulate Gedcom records | 1.15 | metacpan |