Package : perl-Dist-Zilla-Plugin-MetaYAML-Minimal > RPM : perl-Dist-Zilla-Plugin-MetaYAML-Minimal-0.1.1-4.mga9.src.rpm
Basic items
| Name | perl-Dist-Zilla-Plugin-MetaYAML-Minimal |
| Version | 0.1.1 |
| Release | 4.mga9 |
| URL | https://metacpan.org/release/Dist-Zilla-Plugin-MetaYAML-Minimal |
| Group | Development/Perl |
| Summary | Generate a reductionist YAML META file for compatibility only |
| Size | 27KB |
| Arch | noarch |
| License | GPL+ or Artistic |
Description
Generally, if you're creating both "META.json" and "META.yml", then
you're doing so purely for compatibility reasons.
In such circumstances, using the same meta-data for both leads to a lot
of cruft in "META.yml"
This "Dist::Zilla" extension is for such circumstances.
However, if you are *only* shipping "META.yml" and NOT "META.json", then
using this extension would be harmful and cause loss of information.
Presently, this extension is a *PROTOTYPE*, and just culls fields
leading with "x_" passed by "Dist::Zilla".
The final behavior may require enhancements to "CPAN::Meta::Converter"
and might be possibly superseded by patches to "MetaYAML" itself.
you're doing so purely for compatibility reasons.
In such circumstances, using the same meta-data for both leads to a lot
of cruft in "META.yml"
This "Dist::Zilla" extension is for such circumstances.
However, if you are *only* shipping "META.yml" and NOT "META.json", then
using this extension would be harmful and cause loss of information.
Presently, this extension is a *PROTOTYPE*, and just culls fields
leading with "x_" passed by "Dist::Zilla".
The final behavior may require enhancements to "CPAN::Meta::Converter"
and might be possibly superseded by patches to "MetaYAML" itself.
Media information
| Distribution release | Mageia cauldron |
| Media name | core-release |
| Media arch | i586 |
Advanced items
| Source RPM | NOT IN DATABASE ?! |
| Build time | 2022-03-20 22:09:05 |
| Changelog | View in Sophie |
| Files | View in Sophie |
| Dependencies | View in Sophie |