|Think about Loose Coupling|
Conflict Between RPM and CPAN Shell Installation Method?by dave_aiello (Pilgrim)
|on Feb 08, 2001 at 00:49 UTC||Need Help??|
dave_aiello has asked for the wisdom of the Perl Monks concerning the following question:
I am attempting to install the new version of the Slash content management system (aka Bender) on a machine running Version 6.2.3 of VA Linux's distribution. This distribution is essentially Red Hat 6.2, and includes Perl 5.00503 installed as an RPM. The Slash installation instuctions tell me to invoke the CPAN shell:
$ 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:
$ 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.