BEGIN {
  @INC = ();
  ...

[download]

...might not be a good idea to clear the @INC array first, because in this case the standard modules will no longer be found (unless you copy all of them into one of the directories specified). 

$ perl -e 'BEGIN{ @INC=(); unshift @INC, ".", "/home/user/perl/lib"} u
+se File::Find'
Can't locate File/Find.pm in @INC (@INC contains: . /home/user/perl/li
+b) at -e line 1.
BEGIN failed--compilation aborted at -e line 1.

[download]

In the typical case, you just want to BEGIN{ unshift @INC, ... }, or use lib ... to prepend additional search paths to the system paths that @INC already consists of...

In reply to Re^2: Secure deployment of binary perl modules by almut
in thread Secure deployment of binary perl modules by KillerDll

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.