dave_aiello has asked for the wisdom of the Perl Monks concerning the following question:
$ perl -MCPAN -e shellThen, to install Bundle::Slash:
cpan> install Bundle::SlashThe problem I ran into was that something in Bundle::Slash, when combined with my settings for CPAN.pm (like prerequisites_policy "follow"?), result in one of the modules in Bundle::Slash triggering the installation of Perl 5.6.0 via CPAN. This occurs in the midst of the installation of Bundle::Slash.
The installation of Perl 5.6 has a number of side effects. Chief among them is an error in the installation of DBI and DBD::mysql. Repeated attempts to install these modules from the CPAN shell fail. One way around the DBI and DBD::mysql problems is probably to install these modules manually. This is what I intend to try later. (Let me know if you think I am off base with this.)
My main question is how to deal with the aftermath of the Perl 5.6 installation? Perl 5.6 appears to be installed:
$ perl -v...but rpm thinks that the rpm called perl-5.00503-10 is installed:
This is perl, v5.6.0 built for i686-linux
Copyright 1987-2000, Larry Wall
$ rpm -q perlShouldn't I be attempting to make the RPM installed agree with the Perl version that is currently being executed? If so, what parts of the configuration do I need to change?
If I simply uninstall the currently installed Perl RPM, I will need to use some technique to force it because of the number of packages that depend upon it in the RPM database.
I do not need the RPM system to manage the tools I use to install, operate, and modify Slash. But, I would like to continue to use RPM to install software that I run as a casual user. If I simply remove the Perl RPM, it seems likely that the package manager will be far less useful, in that it will not have dependencies that reflect reality anymore.
I would be happy to provide more information, if that would help.
Chatham Township Data Corporation