Tue Aug 24 14:07:40 2010: Request 60697 was acted upon.
Transaction: Ticket created by DORIAN
Queue: PAR-Packer
Subject: Switch to pp pack only architecture-independent (pure-perl) code
Broken in: (no value)
Severity: Wishlist
Owner: Nobody
Requestors: dor...@cpan.org
Status: new
Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=60697 >
Hello,
I propose that PAR::Packer be given a switch to strip out
architecture-dependent (i.e. XS) modules from the dependency inclusion
list when packing a PAR. If I missed a method of doing this, then please
direct me to it.
My use case is that I want to use PAR to bundle up (a Catalyst app
containing) data and modules that aren't on CPAN and deploy the result
on a different architecture (Windows/AMD64). It seems that the system
gets easily confused as to which module to use (namely DynaLoader
version mismatches) and I would prefer to just leave the XS modules out
of the bundle. Setting -m appears to pack all modules, even the
pure-perl ones, into an architecture-dependent directory (pp 1.006).
I would prefer to avoid trying to cross-compile a multi-arch dependency
tree or anything like that; I'm perfectly content to install whatever XS
modules the system requires to run. I'm mostly interested in using PAR
to abridge the effort of managing data files and non-CPAN modules.
Let me know what you think.
Thanks,
Dorian
