On Mon, Feb 12, 2001 at 01:03:31PM -0600, Jarkko Hietaniemi wrote:
> The problem of unpacking, or in other words, installing, or in other
> words, embedded hardwired paths is hard. Think library paths: both
> pure Perl libraries *and* shared libraries. In theory this is easy:
> the portable (and grody) solutions is to have a "long enough" filler
> path(s) that is(are) then at install time binary patched. In
> practice, though, for some reason no one seems to have done this so
> that this would be a widely used practice and well-known art.
Looked at the ActiveState Unix installer lately? They distribute a
Perl binary with a built-in @INC prefix something like
"/tmp/XXXXXXXXXpErLXXXXXX" and then do some s/// madness over the
binary.
Anyhow, this is easily solved by having pun run the scripts inside the
par as "perl -Ilib" or something similar.
Shared libraries are easy enough to solve, build perl staticly linked.
You have to do that anyway to solve the "what version of glibc are you
using" problem (and others).
