I don't get this argument. We always tell people to download the whole world from CPAN, even offering how to use modules if you can't install them the place your sysadmin does.

But going to CPAN and getting perl itself is somehow a big NoNo?

It's not so much a "NoNo" as potentially a lot of work for the testing staff and/or the sysadmins.

If you install a new module from CPAN, that module can't break your existing code, because there isn't any. No additional testing is needed to prove that you can safely promote your code.

If you need to upgrade an existing CPAN module, you will need to do some extra testing to in order to prove that the new version doesn't break any existing production code which uses that CPAN module.

If you need to upgrade perl itself, you need to do a lot of extra testing to prove that the new version of perl doesn't break any existing production code that uses perl.

Depending upon how much perl code is in production, this can be a lot of extra work. I've seen a new installation take several weeks to approve and complete.

Whether or not it's worth it to do that work is a business decision: based upon some kind of a cost/benefit analysis of the relative merits, costs, and risks.

In reply to Re^4: Some trouble with closures by Anonymous Monk
in thread Some trouble with closures by spx2

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.