If you are building your own Perl from source, you should be able to find a solution.
Unfortunately, it's been ages since I've done any of this, but as indicated here I used to build Perl (and many CPAN modules)
from source on about 10 different Unix flavours and bundle it with our product in such a way that
our product did not touch the customer /lib or /usr/lib.
To achieve this (and to avoid the dreaded LD_LIBRARY_PATH), I'm pretty sure our install script binary-edited our executables,
replacing their artificially long build PATH with the customer chosen install directory (with our lib sub-directory appended).
A few random nodes that might give you some ideas to try:
Sorry I can't be of more assistance just threw this out there in case it gives you some fresh ideas to try.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
