Frank Wiles wrote: > I believe this is how Sophos' PureMessage
installs itself. Basically > putting your own Perl binary and
module paths in > say /usr/local/myapp/bin/perl. This is
probably the best way to > ensure you have full control over
everything about your application.  I actually imagine that
Sophos does it exactly the same way ActivePerl does it; until
recently they owned ActiveState, and thus had access to the
ActivePerl setup scripts :-)  FYI, it's not just @INC and binary
- there are also changes needed, for example, in Config.pm, or
you won't be able to install new modules to your new perl
site...