in reply to CPAN.pl... hmmm..

DateTime::Locale and DateTime are two different modules. You have found from perldoc perllocal that module DateTime is at version 0.47, but what about module DateTime::Locale?

Can you update module DateTime::Locale?

It can be difficult mixing modules from distribution packages with modules installed directly from cpan. You might think about installing all your modules from packages.To fix the ones already installed (if they are broken by conflicts) you can force a re-install of the package from the repo. If you want to install modules from CPAN yourself (e.g. the packages are not as up-to-date as you want to be) you should build and install your own perl. It takes a bit of time but it isn't very difficult.

Replies are listed 'Best First'.
Re^2: CPAN.pl... hmmm..
by tweetiepooh (Hermit) on Mar 25, 2009 at 11:22 UTC
    I'd second that, choose repository or CPAN. The first module I get in is CPANPLUS.

    The advantage to packages is it will bring in non Perl/CPAN dependencies like libraries and tools and the installer can plop them in as root for you. I also find that some modules don't build very well in CPANPLUS. I tend to use CPANPLUS to grab the code then build them manually. This is often due to being behind a firewall so testing fails or sometimes with accessing databases. (The worst was Math::PARI and needing to build the pari lib on Solaris 8)

Re^2: CPAN.pl... hmmm..
by partymeeple (Novice) on Mar 25, 2009 at 06:44 UTC
    crikey!! i see now.. thanks for the advice.. as you stay i may stick to the repos if i can. finding the CPAN mods has been a revelation (ie.. i use to pass all my data by hand instead of using the CGI mod). but it's frustrating getting it to work localy.
    beware the farmers.
      Maybe that was just a poor example, but if you have to go to CPAN to get CGI.pm, then you probably haven't had repos to grab from either. CGI has come 'in the box' with Perl for quite a while now I think.