It depends on how you view the OS. Here, I view it as a platform to place my application stack over. IT has responsibility for the OS, I have responsibility for the application. Since the goals and needs of IT at the OS level and my team at the application level are similar, but never identical, I have found that including the runtime environment within my application installation provides a much more stable and reliable application for my users. If the OS de jour changes (as it may), it also gives us (assuming proper isolation of the OS touch points) the ability to migrate while minimizing porting effort (a lesson learned the hard way).

Add into that vendors for part of my application environment that require a specific version of Perl (binary library distribution), and I actually have multiple versions of perl in my application stack. One for each vendor's required version, and one for my overarching application. The parts communicate along well-defined lines of demarcation, allowing for a smoother update process for each component. An additional benefit along for the ride is also being able to move part of the environment to another machine and basically being able to change the location of the resource.

It took me many years and may head/heartaches to settle on this configuration, but it seems to work quite well.

--MidLifeXis

In reply to Re^3: Upgrading perl under AIX issues. by MidLifeXis
in thread Upgrading perl under AIX issues. by twieckow

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.