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

Re^2: CPANP (CPAN Plus) failing?

by HelenCr (Monk)
on Mar 05, 2013 at 01:32 UTC ( #1021734=note: print w/replies, xml ) Need Help??


in reply to Re: CPANP (CPAN Plus) failing?
in thread CPANP (CPAN Plus) failing?

Corion: indeed, that PC has two different installations of Perl.

So, should I go:

perl -MCPANPLUS::Configure::Setup -e 'CPANPLUS::Configure::Setup->init()'

like it says here?: http://cpanplus.sourceforge.net/faq.html#r

Many TIA - Helen

Replies are listed 'Best First'.
Re^3: CPANP (CPAN Plus) failing?
by marto (Bishop) on Mar 05, 2013 at 09:46 UTC

    I suggest you stick to using one Perl distribution to avoid confusion. Different distros have different modules packaged. Recently this problem. Note that both Strawberry Perl and DWIM perl have a C compiler. Consider thoroughly reading the docuemntation for modules before attempting to install them, or their prerequisites.

Re^3: CPANP (CPAN Plus) failing?
by Corion (Pope) on Mar 05, 2013 at 09:33 UTC

    I wouldn't know. I don't use cpanplus. But if their FAQ suggests it, I would investigate that way of solving things.

      For the benefit of PerlMonks users: I went (in cpanp):

      CPAN Terminal>s selfupdate enabled_features

      and it fixed the problem.

      Many thanks to Corion and marto for your help - Helen

        ??enhanced_features??
        CPAN Terminal> s selfupdate enhanced_features To update your current CPANPLUS installation, choose one of the these +options: s selfupdate all [--latest=0] [--dryrun] s selfupdate core [--latest=0] [--dryrun] s selfupdate dependencies [--latest=0] [--dryrun] s selfupdate enabled_features [--latest=0] [--dryrun] s selfupdate features [--latest=0] [--dryrun]

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1021734]
help
Chatterbox?
[Corion]: haukex: Hmm - maybe I can reuse that. I see that it uses Pod::Parser, which I think was one of the more fragile parsers. But if I'm statically (re)generating the tests instead of doing that "live" on the client/tester machines, that's a much smaller...
[Corion]: ... problem space than trying to cater to all versions of Pod::Parser(s)
[haukex]: I think you're right, I think Pod::Simple is the preferred parser now
[haukex]: But I was just using it as an author test anyway
[Corion]: haukex: Aaah - I thought you were still running these tests on every machine, but you only run these as author or Devel::Cover tests
[Corion]: haukex: Yeah, I think back then I used Test::Inline, which used a pod parser that was going through some changes and I didn't want to cater for all the various versions and thus stopped testing the Pod completely
[choroba]: I usually do this with presentations
[Corion]: But now I think statically (re)generating the Pod tests is a saner approach, and likely I'll regenerate the tests either in Makefile.PL or from xt/ but have them live below t/
[choroba]: I keep the snippets in files of their own, and use a Makefile to syntax highlight them and insert them into slides, while also running them and inserting the output if required
[Corion]: choroba: Ooooh - I didn't think of that! I write my presentations as POD and if it "roughly" looks like Perl code, I should also syntax-check that...

How do I use this? | Other CB clients
Other Users?
Others pondering the Monastery: (10)
As of 2017-02-27 12:22 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Before electricity was invented, what was the Electric Eel called?






    Results (385 votes). Check out past polls.