It all comes down to why we've ended up with this version of Perl being distributed by RH. If they had legitmate reasons for compiling it in that way, then I guess it's fair enough. If it's an error on their part, then it's something they should fix immediately.

That said, even if they did have specific reasons for breaking Perl for everyone else, then maybe they should've shipped with 2 versions of Perl, one used by their code, and one for general use.

I can't really accept that a barrier to using Perl should be that you have to compile it yourself. Are we trying to drive people away deliberately? How successful would Linux be if everyone had to compile their own kernel (even for commercial use)?


In reply to Re^3: blaming perl for not using a build policy by Mutant
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.