For those who do not follow the link, the upshot is that rather than go with the standard released version, Red Hat decided to go and add random patches that were floating around. He discovered this because a Red Hat user ran into resulting bugs in the wild. The core Perl sources were patched in November, 2007, but Red Hat doesn't understand or care enough to issue a system update.

He's also really not happy that Red Hat tracks bugs in its bug tracking system but doesn't see fit to share information with the originating communities. So, for instance, when this bug in Red Hat's Perl (not in any version of Perl the Perl folks have released, but it is in Red Hat's version) had the bug reported they closed the bug report saying, "upstream patch". Which doesn't acknowledge that it was a patch they shouldn't have been integrating in the first place, and doesn't tell the upstream folks that there is a bug in an upstream patch that maybe, just maybe, they'd like to fix.

That said, I can understand Red Hat being cautious about replacing the Perl they ship. Lots of things depend on Perl, lots of things are compiled against Perl, and so even an innocuous looking patch has a possibility of creating its own bugs. There is a certain sysadmin mindset that looks at that kind of situation and says, "It is better to leave the problems we know about rather than create new problems." Of course when you combine that mindset with an, "Ooh, shiny!" attitude towards including unstable stuff and you get one of the reasons why I personally prefer Debian-derived distributions.

In reply to Re^2: blaming perl for not using a build policy by tilly
in thread blaming perl for not using a build policy by trwww

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.