Personally, my main Perl is a recent build that I complied myself and keep in /opt (sh Configure -de -Dprefix='/opt/perl5.xx'). That way, I can install CPAN modules into it without the worry of messing up the system Perl, and the modules are in the same directory tree as Perl itself, so I generally don't have to worry about version mismatches. Additionally, when I need a specific Perl version, I use perlbrew, which basically has the same effect of a self-contained Perl, except its environment variables can be applied temporarily. Otherwise, I agree with Fletch to stay away from the system Perl and instead use #!/usr/bin/env perl and PATH to point your scripts at whatever Perl you like. If you do want to install modules into the system Perl, use the system's package manager to do that (though that might not provide all CPAN modules or the latest versions) - I do this on older Raspberry Pis because compiling things there is very slow.
-
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.
|