You can always use relative paths here. E.g. use lib '..';

Another poster also mentioned the viability of the PERLLIB environment variable to override the default @INC. This is not guaranteed to be secure, though, so it will not work if your CGI is using Taint checking (-T).

As far as other users being able to examine your code and see where your libraries are, by seeing the use lib arguments or the value of @INC, I don't see what the big deal is. They can already see your code anyway.

Regardless, with big projects, you really should use relative paths in your use lib statement, just so that it's portable. You can move your app elsewhere without having to re-do all of that. Application-specific/bundled libraries should be referenced via use lib.

In reply to Re: @INC Revisited by Fastolfe
in thread @INC Revisited by Hans

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.