I think the system's perl belongs to the system and you should not be doing stuff like installing non packaged perl modules and running your production application with it.
I disagree. If an OS depends on a certain version/build of perl (or python, or whatever), then they shouldn't put it in /usr/bin/perl.
Solaris got this one right (assuming they haven't changed their policy, it's been a while since I last used Solaris). They too have quite a number of scripts that may break if you replace the default perl. So they put perl somewhere else (say /some/path/to/perl) and start their programs that use perl with #!/some/path/to/perl. /usr/bin/perl is then a link to /some/path/to/perl. Now, if you want to put your own perl in /usr/bin/perl, you can do it. The systems scripts will not refer to it, and they'll keep using the default perl that came with the system.
-
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.
|