Re^2: modules and perl versions

[twoson]

I guess "reluctant to upgrade" describes me quite well.
I like the modules, libraries, configuration, etc that I have.
I usually "upgrade" when I get a new machine and go through the whole new config when that happens.
I just like what I have and am hesitant to upgrade, only to find that other things I may have working might now fail on me.
I also have some production code that I could not afford to lose or have stop working. Getting Geo::Coder to work in my existing environment is my preferable choice.

Another responder wrote "Is it possible this is just the download cache, and that you've yet to make and install these modules?"
If that's the case, then I'm completely up the river as, I've always relied on the ActiveState PPM to do this for me. I've *never* had to do the make - make-install - make-test stuff. This scares me!

[rkrieger]

> I also have some production code that I could not afford to lose or have stop working.

That is an understandable reason to delay upgrading. I do recommend you test whether your application will remain to work with an upgraded system.

> I've *never* had to do the make - make-install - make-test stuff. This scares me!

I can heartily recommend reading the documentation before venturing into stuff that scares you. That usually alleviates the scariness. CPAN is not that hard to deal with and is a great tool once you get the hang of it. In fact, it caters for an 'install $package' interface.

My ActivePerl (v5.6.0, with MS Services for Unix) installation on Win32 is currently broken, so testing whether I can get CPAN going myself is currently somewhat problematic. Fixing it isn't too high a priority either, since I mostly use OpenBSD for my Perl work ;)