Re: Perl upgrade @INC help

I think you're thinking that the modules themselves will somehow be
copied or re-installed. When you install a new version of perl, it
will include some new modules, but extra modules that you've installed
won't be changed.

Yes, I was thinking this. Now I think that a new perl will be installed
in a different location, leaving the old perl as it was, in it's glory
with the old modules untouched. I think ;)

If you want to use an old module "whether it breaks or not", you can
include a 'use lib' line that tells the new perl where to find it.

use lib '/path/to/old/module/directory/';
use Some::Old::Module qw{ from that directory };

That's what I've done in the past, and as stated above, it seems things
will install a new Perl binary with it's own new stuff without
disrupting what I have currently.

So it seems as though I can 'test' my old modules and libs selectively
against the new perl before I implement it across the board. That
understanding is what prompted me to relax and grab the drink :)

You can and probably should test the new binary on
your old programs before you install it.

Thanks for confirming. Off to fetch another pint.

If so, if they do break (particularly the in-house ones), will
warnings/strict throw errors as to what I need to patch?

Maybe! In your situation, I'd probably build a proper distribution out
of the in-house modules, and I'd start putting together a test suite.
Without tests, nobody knows whether the modules are already broken.
Still, chances are good that the modules will work just as well (or
just as poorly) under the new perl.

Well, the old modules I speak of aren't mine, and the coder's scripts
previous to me have no knowledge of strict/warnings, so I've been
hacking them in order to be able to code with and around them, bypass
them and fix them in order to produce results from them that are
expected, and of course this has to always happen live in production.

Make sense right?

We'll see what happens. I can't blame the last coder that was in my
position, as he was coding as he learned, just as I am. I just hope that
I'm being a little better...

Thanks,

Steve
.

Relevant Pages

  • Re: attempt to build 64 bit on Solaris fails
    ... > libraries needed to link with a 64-bit Tk. ... We were running a 32-bit version of Perl ... > Each section below is a summary of the commands used to install it. ...
    (comp.lang.perl.tk)
  • Re: attempt to build 64 bit on Solaris fails
    ... libraries needed to link with a 64-bit Tk. ... We were running a 32-bit version of Perl ... Each section below is a summary of the commands used to install it. ...
    (comp.lang.perl.tk)
  • Perl on Linux and SQL Server 2000 on Windows
    ... There was a time when I did a lot of searching on ways to use Perl ... sitting on Linux to connect SQL Server 2000 sitting on Windows. ... cpan> install DBI ... Install FreeTDS ...
    (comp.os.linux.misc)
  • RE: Please Help !!! Unable to install DBD-Oracle ( I am using perl 5.6 on solaris 8)
    ... Ron, I could be way off here, but the OP mayalready have Perl ... think the original issue was that he tried to use *PPM* to install ... I don't have any Solaris ... you are not the intended recipient, please notify the sender at Wipro ...
    (perl.dbi.users)
  • Re: Installing DBD::File via CPAN
    ... Do you use 'UNINST=1' in the build options for CPAN? ... >> Did you build Perl from source, or install via a RPM or binary distro? ... >>> sender of the delivery error by replying to this message, or notify us ...
    (perl.dbi.users)