From: Carlos Sevillano (carlos_sevillano@ureach.com)
Date: Wed Dec 11 2002 - 14:53:07 EST
Solaris 2.6
Perl 5005.03/5.60
to
Perl 5.6.1
I have an old system running perl 5005.03.
At some point someone updated perl, just the
perl binaries and libraries to Perl 5.60
(perl -v shows 5.60 - Pkginfo shows perl
5005.03). I am building a new system and
need to migrate what they have perl-wise to
the new system running Perl 5.6.1.
The problem is that I ran into a buch of
modules that were available under 5005.03
that I have to update on the new
installation. These modules work with the
Perl DBI and Perl DBD and many custom perl
modules to act as an "application".
What is the right way to migrate all these
modules? Do I have to collect them from the
CPAN and do a a native install ... can they
be copied from the old system to the new
one? Here are the modules in question:
Net::Ping;
Net::Telnet::Cisco;
Net::FTP;
Tie::SecureHash;
Proc::ProcessTable;
Date::Calc;
Data::Dumper;
The modules are not part of the standard
Perl distribution, they are not available on
the clean perl installation (some of them
like Tie are, however, the SecureHash part
is not). Can I just copy everything by hand
from the old machine? I am not sure why,
however, some of them are on multiple
locations on the old machine:
old system:
Tie::SecureHash; = SecureHash.pm
/usr/local/bin/Tie-SecureHash-1.03/SecureHash.pm
/usr/local/bin/Tie-SecureHash-1.03/blib/lib/Tie/SecureHash.pm
/usr/local/lib/perl5/site_perl/5.6.0/Tie/SecureHash.pm
Net::Ping; = Ping.pm
/usr/local/bin/perl-5.6.0/lib/Net/Ping.pm
/usr/local/lib/perl5/5.00503/Net/Ping.pm
/usr/local/lib/perl5/5.6.0/Net/Ping.pm
Net::Telnet::Cisco; = Telnet.pm
/usr/local/bin/Net-Telnet-3.02/lib/Net/Telnet.pm
/usr/local/bin/Net-Telnet-3.02/blib/lib/Net/Telnet.pm
/usr/local/lib/perl5/site_perl/5.6.0/Net/Telnet.pm
Net::FTP; = FTP.pm
/usr/local/bin/libnet-1.0703/Net/FTP.pm
/usr/local/bin/libnet-1.0703/blib/lib/Net/FTP.pm
/usr/local/lib/perl5/site_perl/5.6.0/Net/FTP.pm
Proc::ProcessTable; = ProcessTable.pm
/usr/local/bin/Proc-ProcessTable-0.27/ProcessTable.pm
/usr/local/bin/Proc-ProcessTable-0.27/blib/lib/Proc/ProcessTable.pm
/usr/local/lib/perl5/site_perl/5.6.0/sun4-solaris/Proc/ProcessTable.pm
Date::Calc; = Calc.pm
/usr/local/bin/Date-Calc-4.3/Calc.pm
/usr/local/bin/Date-Calc-4.3/blib/lib/Date/Calc.pm
/usr/local/lib/perl5/site_perl/5.6.0/sun4-solaris/Date/Calc.pm
Data::Dumper; = Dumper.pm
/usr/local/bin/perl-5.6.0/ext/Data/Dumper/Dumper.pm
/usr/local/bin/perl-5.6.0/lib/Data/Dumper.pm
/usr/local/lib/perl5/5.00503/Data/Dumper.pm
/usr/local/lib/perl5/5.6.0/sun4-solaris/Data/Dumper.pm
One more question... how does perl know
where these modules are located.? I know
how perl is calling them Use Net::Dumper. I
am not sure how perl knows that the
Data:Dumper module is in any of the four
paths mentioned below?
Data::Dumper; = Dumper.pm
/usr/local/bin/perl-5.6.0/ext/Data/Dumper/Dumper.pm
/usr/local/bin/perl-5.6.0/lib/Data/Dumper.pm
/usr/local/lib/perl5/5.00503/Data/Dumper.pm
/usr/local/lib/perl5/5.6.0/sun4-solaris/Data/Dumper.pm
Is that information built into perl when you
compile the module using "perl Makefile.PL;
make, make test; and make install"?
Carlos
________________________________________________
Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:25:27 EDT