Beefy Boxes and Bandwidth Generously Provided by pair Networks Ovid
Perl: the Markov chain saw
 
PerlMonks  

Comment on

( #3333=superdoc: print w/ replies, xml ) Need Help??
1. It's in very rare events that CPAN modules need to be uninstalled, in my experience manually deleting the .pm/.xs, etc files in @INC works best. Although, you see many people will disagree and have gone so far as to write modules to assist in this operation.

2. Configuring CPAN is a necessary burden, also I don't think closing your eyes and picking a random mirror has a significant impact, I just choose the well-known (or seemingly well known) mirrors.

3. Some CPAN packages in the debian package pool are outdated, some by months/in excess of 2 or more revisions. I was amazed to find out just how many seem are actually outdated when i used the CPAN shell to upgrade. Also, debian-perl maintainers might be inclined to choose a different package to satisfy a dependancy when infact you might already have the necessary header files available locally (from other source or debian packages). In my opinion, CPAN/CPANPLUS seems to be the way to go - configuring from source and all that, it's definitely longer and sometimes requires manual interaction but since CPAN.pm is a perl module, it means installing perl modules from within perl script is possible.
#!/usr/bin/perl -Wl use CPAN; while (<DATA>) { chomp; install $_; } __DATA__ Foo::Bar Foo::Baz Foo::Quux
5.  perl -MCPAN -e upgrade
6. CPAN isn't as bleeding edge as CPANPLUS but it's definitely still chugging along. Michael Schwern, author of Module::MakeMaker seems to suggest using CPANPLUS vehemently, quite plausibly because CPANPLUS has better support for Module::Build and also because it's just pretty much better structured than CPAN (which could do with a complete rewrite). I should think CPAN and CPANPLUS will continue to live on contending, just as GNOME/KDE, Firefox/IE, etc.

7. It's quite hard to botch up on installing perl modules, even if you should, leaving them be isn't going to impact you in any significant way unless they were incompletely installed. In any case, using a 'forced install' of CPAN::install() seems to effectively reinstall those modules (with the added disadvantage of test errors being turned into warnings).
perl -MCPAN -e shell # or /usr/bin/cpan > force install Foo::Bar Foo::Baz Foo::Quux

In reply to Re: help managing modules using CPAN.pm by Anonymous Monk
in thread help managing modules using CPAN.pm by j3

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!
  • 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
  • Outside of code tags, you may need to use entities for some characters:
            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?
    Username:
    Password:

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

    How do I use this? | Other CB clients
    Other Users?
    Others taking refuge in the Monastery: (8)
    As of 2014-04-17 05:34 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      April first is:







      Results (439 votes), past polls