Jarkko Hietaniemi wrote:
I really don't think we should have Perl data structures in files
(that means Perl code, right?), because that indicates doing an eval,
and I don't want to eval any more random code off the 'net than
necessary.
Consumers of META.yml may be separated into two groups:
- those who really don't want to eval perl code (i.e. search.cpan.org,
cpants, cpan deps etc.)
- those who don't care to eval perl code, because they do it anyway in
the same process (i.e. when installing a CPAN distribution with
CPAN/CPANPLUS)
Therefore I think the current approach of dumping to a yaml file should
be preserved for the first group, and dumping to a perl file added for
the second group. This has also the benefit that there does not need to
be any discussions whether to add YAML::Tiny, YAML, or JSON or whatever
deserializer to the Perl core.
Regards,
Slaven
On Fri, Oct 9, 2009 at 8:14 AM, Ricardo Signes
<perl.cpanw...@rjbs.manxome.org> wrote:
* David Golden <xda...@gmail.com> [2009-10-09T07:44:43]
06. Data structures, not YAML
Proposal:
The META spec should be defined in terms of (Perl) data structures, and not
in terms of YAML. (Slaven Rezic)
Agreed, but the spec should be very clear (perhaps, as said, in an appendix)
how the data should be serialized and included in dists.
--
rjbs
