Upgrades have consequences. I can't speak for the 5.6.0 -> 5.6.1 Test::Harness problem but I do recall that you cannot just upgrade to 5.8.0 and expect compiled modules to work. Some binary APIs were changed or something - it's in the ChangeList or somewhere prominent that I know I read about it. All that means is that if you upgrade to 5.8 you can expect to have to somehow conspire for either all the compiled stuff to get recompiled or just install them over again.

In addition to that - keep in mind that any fool can upload new things to CPAN. People can't overwrite each other's work but there's nothing to stop someone from sending /new/ things up. This means there's some inherant trust issues regarding modules from CPAN. You have to trust that the author is both cluefull and benign. I do place a lot of trust in the various authors who publish to CPAN. The only alternative is to either audit all the code I download or just not download it. Both are fairly poor alternatives.

There is one mitigating factor: CPAN testers. There's already a great bunch of people out there downloading and trying new versions on their various machines. There's at least a chance that any problems will be at least noticed if not caught by these folks. If you follow the URL I just posted then you'll also notice an archived e-mail list of testing results. Those results are gathered back into CPAN proper and are visible when viewing the CPAN archive from search.cpan.org.

This leaves with some options - you can either approach CPAN with the appropriate wariness and use the tools provided (CPAN tester's results, is it a common module, ChangeLog info on incompatible changes) or you can continue to operate in a fantasy land where every new change and tweak is backwards compatible and is bug free.

__SIG__
printf "You are here %08x\n", unpack "L!", unpack "P4", pack "L!", B::
+svref_2object(sub{})->OUTSIDE

[download]

In reply to Re: Module installation can be harmful by diotalevi
in thread Module installation can be harmful by toma

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.