Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Your question depends on a lot of factors, mainly, is this a development box? Is this your home account? etc.

Personally, I roll my own perl and cpan what I need so I have a very clean (well, clean enough) development environment that is completely separate from the operating system's idea of what it needs. Sometimes when you are supporting existing code, you need your environment to match as closely to what existed when you released. If you are like me and like to keep your OS updated weekly to catch patches and new features, you soon realize that using the OS to manage your perl installation can be hazardous.

Linux distributions in general apply patches to the things they use internally. This includes perl modules. That means bad things can happen if you rely upon a certain behavior in a certain module, and the distro maintainers pull the rug out from under your feet with a patch.

It really doesn't require that much effort to compile perl from source with a prefix that points to a location separate from the rest of the OS (ie. in your home directory with your exec path set to ~/bin or whatever). This way in a multi-user environment two users can require two different versions of a particular module with the operating system requiring a third and if they all have their own space, everyone is happy.

In reply to Re: yast vs cpan by nicholasrperez
in thread yast vs cpan by elnino2007

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 scrutinizing the Monastery: (1)
As of 2024-04-25 04:27 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found