| CC: | h.m.brand [...] xs4all.nl |
| Subject: | Documentation for meta-spec version is confusing |
The documentation says this about the "version" subkey of the meta-spec key:
This subkey gives the integer Version of the CPAN Meta Spec against
which the document was generated.
That doesn't look right to me. First, the Version type is defined as
things that version.pm can parse. That implies that the meta-spec
version could be 2 or 2.1 or 2.1.1. Second, the current version is "2",
but earlier versions have been "1.4", "1.3", and so on. Third, the
default value if you do not specify a meta-spec version is "1.0". So
the meta-spec version can't be limited to integers, as the docs suggest.
But my real dillemma is this:
https://metacpan.org/source/HMBRAND/DBD-CSV-0.34/META.json
In that file, the meta-spec version is "2.0" not "2".
CPAN::Meta::Validator won't accept that because it doesn't match the
keys of any of its %definitions. I think the meta-spec version needs to
be normalized and stringified with version.pm before looking it up in
the %definitions.
But the choice of "2" for the current version seems very deliberate, so
perhaps I'm missing something here.
Thanks for your time.
-Jeff