On 25-Aug-10, at 1:36 AM, Dave Howorth wrote:
This is a discussion that belongs on par@perl.org rather than a bug,
isn't it?
I sent a message <mid:72421211-a3e4-4226-9da1-5aa1290f6...@gmail.com>
two weeks ago that didn't get an answer. I rated the "bug" as
"Wishlist". Did I misstep somehow?
Dorian Taylor via RT 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.
It seems to me that what you're looking for is a switch guaranteed to
produce broken distributions.
I don't care if the distribution is "broken". This is for my
convenience (read: the opposite of a complete slog). I see value in
being able to create PARs intended for a private target that are
composed of a partial set of dependencies, for which the target system
compensates. I am frankly surprised this has never come up before.
If you want to produce a pure-perl distro
that will work on Windows, then start from a pure-perl installation,
not
one that uses XS-based modules.
Cute, but easier said than done. A non-trivial amount of well-trodden
modules (e.g. Moose) appear to have an XS component.
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.
So I'd suggest you code it up and show everybody. That may resolve
people's doubts about the worthiness of the idea.
I floated this idea before sitting down to code to see if there was a
modicum of consensus. I am puzzled by the contention. If I submit a
patch, will it get integrated?
There've been a couple of useful suggestions about possible
implementations.
Cheers, Dave
Thanks for your concern.
