Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

Update: Excellent points made in responses. A rewrite is in the works. Keep them coming.

Perhaps this is a tutorial, or perhaps something that just belongs long term in Meditations, but my intent with this node is to document the arguments related to modifying the system's Perl installation, so that I don't have to lay out the argument every time it comes up in SoPW. There are some pro, and some con, but it seems to be, in my experience, that "Can't touch this", if given the choice, is the correct path to take.

Some of the previous comments I have made on this topic can be found here: SuperSearch Preload

So, without further ado, here are some arguments in favor of installing your own Perl (in no particular order):

  • Modifying the system Perl can break the OS.
  • Updating the OS can change the underlying Perl, breaking your application.
  • You don't necessarily have control over the system's Perl.
  • Updating the system's perl for application's needs can go against another application's needs.
  • The system's Perl may not be complete.
  • By packaging Perl with your application stack, you control the installed modules and toolchain.
  • It is easier to target a single Perl version than anything you might find on the OS.
  • Policy may disallow installing a "necessary" module on the system's Perl.
  • Your installed / updated CPAN modules may be overwritten (and downgraded) by OS updates. - Corion
  • You are (safely) limited to the module versions provided in packages by your vendor - Corion

There are also some cons to installing your own Perl:

  • Your application distribution now requires or includes a separate Perl distribution.
  • Your packaging requirements are now more complex.

In summary, unless you are writing an OS-level tool specifically for this platform, install a Perl version specifically for your own application's runtime stack.

Anything else? (ed: updates tagged with author)

--MidLifeXis


In reply to RFC: (Do Not) Modify the System Perl by MidLifeXis

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (3)
As of 2024-06-15 11:29 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found

    Notices?
    erzuuli‥ 🛈The London Perl and Raku Workshop takes place on 26th Oct 2024. If your company depends on Perl, please consider sponsoring and/or attending.