Side note...

I've faced this problem. I tackled it. (With actually some good help from my first line manager - possibly higher, I'm not sure.) We now have multiple versions of perl in production. Older code uses older perl, new code uses newer perl. In fact, my code runs on perl 5.8.7 on Unix/Linux and 5.8.6 on Windows (due to a problem we had on unix/linux which wasn't relevant to windows - no desire to upgrade windows again), while the code from other teams runs on 5.8.1 or 5.6 or even 5.005.

The 5.8.7 install has the 5.8.6 lib directories in its hardcoded @INC. The lib directories are shared across all platforms (including Windows, I think). And I have a way of hacking in new CPAN modules at runtime (thus far, they're all pure perl which makes it trivial, not sure if I'm brave enough to try XS or Inline::* code...).

This is a fairly large software company. (Our building has about 2500 people - software developers and support, such as IT, management, customer service, HR for software development, but not sales, corporate management, lawyers, etc. And we're not the only developers in the company.) It's just a matter of aligning the priorities and making sure everyone gets what they want. Management wants to ensure nothing is broken. Thus, keep the old versions of perl. Management also wants fast development. Thus, new versions of perl need to coexist in a way that allows us to get new CPAN modules.

I actually got this ball rolling when we started investigating XML-based technologies. There was no way I was going to do that by hand - I got my manager behind the idea that we needed XML::Twig. And we pushed from there - "No way to hit our dates without this." As in, yes, we can do it, but not by the end date you want it to be done by. That brought extreme amounts of pressure to resolve the situation.

Of course, if your management says, "Ok, we'll move out the dates," then that's what you do. You rewrite stuff that would work fine if they were willing to have a parallel perl that was up to date. But they're willing, instead, to pay you to reinvent some wheels. That is their perogative. ;-)

In reply to Re: Why non-core CPAN modules can't be used in large corporate environments. by Tanktalus
in thread Why non-core CPAN modules can't be used in large corporate environments. by Moron

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.