Tue May 19 11:21:23 2015: Request 104509 was acted upon.
Transaction: Correspondence added by ddca...@gmail.com
Queue: PAR
Subject: Re: [rt.cpan.org #104509] Problem signing PAR file
Broken in: (no value)
Severity: (no value)
Owner: Nobody
Requestors: ddca...@gmail.com
Status: open
Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=104509 >
Hey Roderich,
Understood on that!
What about compiling a list of 'problematic modules' and giving PAR the
option to fix them? It might be a nice addition to the platform. The Encode
module is another tricky one. It has many dependencies but they are only
called when needed and so do not get appropriately packaged.
In the meantime, the MANIFEST fix for the addfiles by Shawn is working and
should probably be included as a fix, but I'm still not having luck with
the Signature module for some reason.
On Tue, May 19, 2015 at 10:12 AM, Roderich Schupp via RT <
bug-...@rt.cpan.org> wrote:
> <URL: https://rt.cpan.org/Ticket/Display.html?id=104509 >
>
> Am 2015-05-19 10:22:38, ddca...@gmail.com schrieb:
> > There's already a bug ticket in for that in ScanDeps from 2013.
> >
> > https://rt.cpan.org/Public/Bug/Display.html?id=91530
>
> Re-reading my own comments...
> Yeah, there are 1001 ways to refer to a data file from a Perl module.
> And most of them break when using PAR. The power of TMTOWTDI, yech.
> (In my dreams I envision there would be only one sanctioned method
> to do this and it could be inspected or intercepted by PAR.)
>
> This can't be fixed solely in Module::ScanDeps, it also needs a rule
> in PAR::Filter::PatchContent, cf. what's been done for Mozilla::CA.
>
> Cheers, Roderich
>
>
