Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked

Comment on

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

I like the variant of (2) that uses special locations in /usr/local for all CPAN installation. This sounds like the easiest way to cover any possible problems, and I suspect that and already do this by default (see below).

Technique (1) on the other hand strikes me as very generally useful: it might be more work, but once you've mastered those techniques you'll find other uses for them (like, for example, you want to try upgrading from perl 5.8 to 5.10 for the production code, but leave 5.8 in use for the system code).

Technique (3) is very Debian/Ubuntu specific, and at a guess is only worth hassling with if you're interested in getting involved with helping the Debian project by maintaining debs of perl modules.

What I actually do, however, is ignore the problem: I install a bunch of debian/ubuntu perl packages, but whenever I'm so inclined I do installations and updates via or I realize it seems like living dangerously (how do I know an "apt-get upgrade" won't downgrade something important?) but I've yet to run into any difficulties like that.

Taking a look at my @INC, I see I've got a rough order of precedence of dev, local, and system locations. Maybe that's a policy that helps. I just experimented with installations via and, and I see they both install in /usr/local/share -- it could be I've got method (2) covered already without realizing it. There's nothing special in my ~/.cpan/CPAN/ that does this, so it would seem that do the Right Thing by default.

This is an experience I've been having lately with perl, by the way... I start worrying about some issue, dig into it, and I find that it's largely a non-issue because someone else did something intelligent a long time ago.

In reply to Re: What is the best way to install CPAN modules on Debian? by doom
in thread What is the best way to install CPAN modules on Debian? by ELISHEVA

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-06-18 19:34 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (110 votes). Check out past polls.