Sat Nov 05 07:09:02 2011: Request 72112 was acted upon.
Transaction: Correspondence added by SMUELLER
Queue: PAR-Dist
Subject: Re: [rt.cpan.org #72112] PAR::Dist META.json problem
Broken in: (no value)
Severity: (no value)
Owner: Nobody
Requestors: po...@dvo.ru
Status: new
Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=72112 >
Hi,
On 11/02/2011 06:39 AM, po...@dvo.ru via RT wrote:
> I've started to use PAR::Dist::FromCPAN to create standalone repository
> for my project, but during
> compilation of some modules it fails. Some analysis show that this
> modules do not have proper META.yml
> file but have META.json. In building time as I can see some data from
> this META.json are stored in MYMETA.yml.
> In the code CPAN::Distribution module I have read that " # if MYMETA.yml
> exists, that takes precedence over META.yml".
> So I've wrote small patch to fix problem with installation.
Indeed. MYMETA.yml is the authoritative source of any dependency
information and other meta info. Its inception was after I last touched
the PAR::Dist code and I don't think anybody else has since.
The problem with MYMETA is ordinarily that it's not available before
building, so most tools can't rely on it. This is different for the part
of PAR::Dist that you care about as it comes in only after build time.
Either way, we may have to eventually add META.json support to
PAR::Dist. The modules currently does many nasty things in order not to
require a YAML parser in order to work out of the box on old perls.
Repeating that for JSON would be horrible. When I spent a bit of time to
think about it, I couldn't come up with a very good solution. If it's
the case that the recent toolchain will always generate MYMETA.yml even
if there was a META.json, then we just bought some time.
I'll upload a patched PAR::Dist 0.48 within the hour.
Best regards,
Steffen
