On any OS that provides a perl you should always compile and maintain your own perl distribution.

That way you do not have to worry about OS patches installing updated Perl modules and breaking your applications and vice-versa.

I just compile perl into /opt/<company>/perl on a build system. Then I install the modules and make a Solaris package from the install directories.

Then this package can be installed into any environment (development, qa, staging and production) and I know that my deployment procedure is testable, repeatable and automatable.

On Solaris I tend to create Solaris packages of my perl applications too, so that my deployments go more smoothly.

--
Clayton

In reply to Re^2: Relocation error when using Log::Log4Perl by clscott
in thread Relocation error when using Log::Log4Perl by Anonymous Monk

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.