Tue Aug 24 15:41:11 2010: Request 60697 was acted upon.
Transaction: Correspondence added 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: open
Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=60697 >
On Tue Aug 24 15:26:01 2010, RSCHUPP wrote:
> On 2010-08-24 14:07:40, DORIAN wrote:
> > 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.
>
> This doesn't make sense to me, at least it doesn't warrant
> a new option to pp (if that's what you meant) - it already
> has far too many options for my taste.
>
> If you have special needs try to tailor what gets packed
> using -m and -X.
My thinking was that in order to do that I'd have to know up front which
modules were XS in the entire dependency graph and which weren't. Unless
I am making gratuitous assumptions, this entails either maintaining a
list by hand or scanning. Since pp already performs this scan, that
information is handy, and it seems a bit of a waste/error-prone to have
to scan twice. I thought it would make sense to be able to, in one shot,
say "omit all XS modules from this PAR".
I'm not trying to make work for anybody here; I'm content to write the
code myself. I find it puzzling that the desire to only pack pure-perl
module dependencies into a PAR has never come up before.
Is there something else I'm overlooking?
