"#!/Users/user/perl5/perlbrew/perls/perl-5.14.1/bin/perl5.14.1"

That shebang line locks the script into using a single version of Perl. While that might be what you want in some circumstances, I don't think that would be the norm.

This shebang line (which I indicated in "Re^3: Can't locate Email/MIME.pm in @INC" below) allows you to upgrade Perl and use it with all your scripts without having to edit every one of those scripts.

#!/usr/bin/env perl

It also makes it easy to test your current codebase with new versions of Perl: a single "perlbrew switch new-perl-version" to check for backward-compatibility and a single "perlbrew switch old-perl-version" to rollback (if that's required).

-- Ken


In reply to Re^4: Can't locate Email/MIME.pm in @INC by kcott
in thread Can't locate Email/MIME.pm in @INC by netperl

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.