in reply to Re^2: perl module installs getting really mesed up
in thread perl module installs getting really mesed up


(You probably already did all of this, I don't want to seem patronizing)

Replies are listed 'Best First'.
Re^4: perl module installs getting really mesed up
by SilasTheMonk (Chaplain) on Sep 11, 2009 at 15:28 UTC
    I have located the config and it is fairly different from the test machine. Nothing obvious jumps out. What is really clear however is that I am not even really sure what I want from the CPAN config. I mean in test at least at the moment I probably want to bang stuff in. So my action plan seems to be:
    • Try installing a private 5.8 version of perl in test.
    • Look at lower memory solutions like CPAN::SQLite.
    • Learn treat CPAN as a friend and get to know it more intimately.
    Maybe one day I will have a budget to throw at the problem, in the meantime thanks to everyone for their help.
      What you want from the CPAN config is that it controls your command line cpan. This is likely not where the problem is- but if the CPAN config is sufficiently f****d up, commmand line cpan won't work.

      (Really? You don't see how the config file would influence the program in any way?)

        CPAN is a complicated module compared to what me as an end user would like it to be. Ideally I would like it not just to read my mind but predict how I would react in unusual situations. I find it frustrating when installs fail. I also have contradictory wishes. Now I think about I see it is entirely possible that I have messed up the CPAN config since: 1.) I have a poor understanding of CPAN 2.) I have not resolved my internal conflicts over how I want it to behave. So it seems at the moment I have to complete a lot of installs manually. I do not like this. However I now realize I need to study CPAN a lot more before I can solve that problem.