I actually get this in private conversations a fair bit lately. The primary reason I hear for its use when other options are being tossed around is that its due to being a corporate setting, where C-level-type folks want something that they have to pay for, because that seems more legitimate. These are organizations that often don't employ any Open Source software (that they're aware of), and a purchase constitutes quality and support.

That said, the majority of the issues crop up because those same people forgo any updates, because that actually hits their budgets, so lower-level staff have to do things like OP is trying to do, and work around these types of legacy issues, which, in (pulling random statistic out of my ass) many cases causes even worse problems in the future until eventually, something needs to be done at a very large scale to rectify all of the custom nonsense, offsetting any perceived 'value' that may have been had when signing an agreement/purchase order.

Fun stuff.

ps. I've never actually used Active State, so I can't say whether it's good or bad. That said, proprietary package manager for Perl? Yeah, no. Seems like a direct vendor lock-in for no tangible benefit at all.

In reply to Re^2: Installing new Perl Modules by stevieb
in thread Installing new Perl Modules by amitsq

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.