Solutions to bypass it would be to create a symlink to the former path, to add it in -I directive when calling perl, add it to the $LIB (not $PATH variable) $LIB is not a perl thing or a perlbrew thing
The simplest solution to not having perlbrew break in the future, is to have one of your perlbrew perls as the first perl in the path, so when you type perl or perlbrew its the one from your home directory that runs, so when you upgrade your OS and your system perl (os perl), your home directory perlbrew installed perl is untouched and works the same
-
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.
|
