Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Note: I didn't write this post to start a flame war or to discredit anyone. What i like to see is some active discussion on the topic

On most of my (linux) systems, i usually have at least two perl binaries installed:

  • Whatever comes with the linux distribution, usually at /usr/bin/perl
  • The one that i use. That's the one a call to "perl" starts in *my* user account

In the past - when using the OS supplied perl - i had some major troubles. Mostly, these where incompatibilities after the distributor rolled out some updates or when i upgraded some modules to newer (test) versions. Also, now i use ActiveState Perl for much of my software development.

The trouble is: While the distribution-supplied scripts correctly call /usr/bin/perl, most of the code that i download from the interwebs does so too - and start breaking because of "missing" modules

The thing that worked for me best is to change all Perl scripts on my system to use
#!/usr/bin/env perl
as the hashbang line. Whenever the systems automatically start a Perl script, it uses the dristribution-maintained perl, whenever i start a script with my user account, it uses the perl installed in my home directory.

In my opinion, in a time where there are more and more different plattforms, assuming perl is at a fixed path and that perl binary is the correct one to use isn't very helpfull. It's similar to the still widely spread believe that /bin/sh is bash (or csh or whatever)...

In reply to Calling the correct perl binary by cavac

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others making s'mores by the fire in the courtyard of the Monastery: (8)
    As of 2018-04-20 13:54 GMT
    Find Nodes?
      Voting Booth?