Hi Rupesh,
Rupesh wrote:
[...]
I want to reduce the size of the binary that is generated.
It was noticed that the size reduced considerably when we used the "-d"
option. What are
the chances that this binary would fail on other machines?
We're running on Linux and it should be assumed that the remote machine has
just plain
linux (with perl) and none of the required modules that the script requires.
Those other machines need a binary compatible perl installation, as far
as I know. That means: If you include any modules that aren't pure-perl,
the installation of perl on the target machine needs to be pretty
similar to what you're packaging on. Furthermore, as pp --help says,
your perl (and the target perl) need to built as a shared library. I'm
pretty sure that's the case on most Linux boxes. (It's also the case for
ActiveState's Windows perl binary.)
If you're including only pure-perl modules and the version of perl on
the target machine isn't much older than yours, -d might actually be a
reasonably safe bet.
Now, if you're requiring a compatible perl anyway, you can skip the
inclusion of the core modules, too, to reduce the size of the archive.
I haven't experimented much with dependent PAR archives, though.
HTH,
Steffen
