Re: META.json: duty now for the future

[Ask Bjørn Hansen]

0) Yay for JSON.

1) Is it really necessary to use ascii instead of just regular utf-8  
for the JSON output?


2) The documentation is a little confusing saying If it can be  
loaded, any META.yml file produced will contain JSON. -- but it looks  
like the code (correctly) makes the output file be META.json when all  
is well.



 - ask

Re: META.json: duty now for the future

[David Golden]

On Sun, May 17, 2009 at 7:36 PM, Ricardo SIGNES
perl.cpanw...@rjbs.manxome.org wrote:
  * update PAUSE to prefer META.json to META.yml if available
  * update CPAN.pm to look at (MY)?META.json
  * update CPANPLUS.pm to do the same
  * update the build tools to generate (MY)?META.json by default
  * update the META spec to demand JSON

After watching yet another dogfight in RT and the M::B list about
META.yml parsing, version objects, etc., I would really, really
appreciate the following as well:

* A single canonical META.json generator and parser -- that all the
tools use and that could reasonably be lobbied into the core.
* Unambiguous META spec for version number formatting
* Spec validation (separate from parsing so it can use non-core tools)
* Have PAUSE reject dists with an invalid spec

-- David