I had to deal with something similar for a site I've worked on. This only works for compiled modules where your machine is binary compatible, though.
I made a directory under my ftp root called perl-mods. I installed the modules on my computer, then moved ftp'd up the ones I needed into my perl-mods directory. You must be careful to keep the paths preserved so they work right, of course. My computer ran Redhat 6.2 and so did the server, so any more complicated modules compiled the same. Modules that are just perl this doesn't matter for.
Then, in all my scripts at the tope I put a use lib /home/mine/perl-mods to use that directory. Of course, I know that is where my home is on the server because the admin was cordial enough to at least tell me that. If you don't know the path to your perl-mods directory, you have a harder time. I think you could put perl-mods underneath your cgi-bin (/cgi-bin/perl-mods/). Then do a use lib ./perl-mods I think that this would work since its a relative path. I know it works with an absolute pathname, and should work for relative too. Not quite the most secure I guess, but might be the best you can get.
-
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.
|
