Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (herse.apache.org: domain of mpeters@plusthree.com
 designates 207.114.11.197 as permitted sender)
Message-ID: <4554829E.4000200@plusthree.com>
Date: Fri, 10 Nov 2006 08:46:06 -0500
From: Michael Peters <mpeters@plusthree.com>
User-Agent: Thunderbird 1.5.0.7 (X11/20060913)
MIME-Version: 1.0
To: Foo JH <jhfoo-ml@extracktor.com>
CC: mod_perl <modperl@perl.apache.org>
Subject: Re: [mp2] PAR in production?
References: <fd1b28650611060701g490b7e77s99a64e1db43de5d9@mail.gmail.com>
  <20061106122859.add1982b.frank@wiles.org>
 <1163008040.30686.16.camel@localhost.localdomain>
 <Pine.LNX.4.64.0611091057260.12541@app.redhotpenguin.com>
 <45537D3E.8020007@plusthree.com> <4553E608.4070608@extracktor.com>
In-Reply-To: <4553E608.4070608@extracktor.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


Foo JH wrote:
> I don't understand. What do you mean by 'perl is not relocatable'? I've
> put (Active)Perl in the same directory as the apache server in a
> copy-paste operation. But this is in Windows.

One example is that @INC is determined at compile time. If you move your perl
around, @INC doesn't change. Having it be truly relocatable means that the
binary can find libraries relative to it's installation rather than being a full
path.

After reading some archives it seems that ActivePerl may already be able to do
this, but I'm not sure.

-- 
Michael Peters
Developer
Plus Three, LP