I've done both, but in either case, compiling your own Perl is the right approach because in the long run, each application should get its own, independent Perl binary. At least unless you can maintain a comprehensive test suite and test environment to ensure that module and Perl upgrades go smoothly, decoupling applications from the Perl version seems to be the best approach to me.

Compiling your own Perl isn't hard, the nasty thing is installing the C libraries that some XS modules want. I don't know if/how BSD or Pair Networks provide such libraries like libxml2 or libexpat - if they don't provide them in a convenient way, you might want to go with the home-hosted version.

In reply to Re: Time for an application portfolio by Corion
in thread Time for an application portfolio by talexb

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.