develooper Front page | perl.perl5.porters | Postings from February 2003

Re: Activestate's post-compile @INC patching...

Thread Previous
From:
Jan Dubois
Date:
February 3, 2003 10:06
Subject:
Re: Activestate's post-compile @INC patching...
Message ID:
ppbt3v4ltvpp84im031sfrct0l826hh222@4ax.com
On 03 Feb 2003 09:43:19 -0800, merlyn@stonehenge.com (Randal L. Schwartz)
wrote:

>I had a client ask me about how Activestate allows you to install
>their Unix binaries "anywhere".  I presume it's done with the "pad
>every @INC element out with NULs" and then an install patchup to put
>the actual paths in there and in Config.pm.  But when I looked at the
>provided "diffs between 5.8.0 and AP804" file, I don't see anything
>that resembles that.  I'm guessing then that it's all done with the
>right configure variables and an install proggy that doesn't have to
>be made available under the GPL.
>
>Is the process to make a binary run anywhere proprietary to
>Activestate, or did I just miss that the sources were out there?

The script that does the relocation is in perl/bin/reloc_perl in the
ActivePerl distribution.  ActivePerl is built with a long silly pathname
(not with embedded NULs), and that path is being replaced during
installation with the actual install path.

Cheers,
-Jan


Thread Previous


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About