On a new server, I wanted to install a few extra perl modules using cpan, so I did "yum install cpan" and then installed 4 perl modules.
Then I did this (maybe it was not a good idea?):
What I wanted to, was to make sure cpan itself and all cpan modules was up to date. However when I run the above "upgrade", cpan installed a lot of perl modules and dependencies, so that when it finished, it is now 135 directories/perl modules in /root/.cpan/build
But all I needed was the 4 perl modules I first installed.
So, should I be worried about this? Was this not the correct way to make sure cpan and cpan modules was up to date? I feel somewhat bad about what just happen, when it installed over 100 modules when I only wanted to upgrade/make sure it was newest versions. Feel confused to!
Then I did this (maybe it was not a good idea?):
Code:
cpan
upgrade
What I wanted to, was to make sure cpan itself and all cpan modules was up to date. However when I run the above "upgrade", cpan installed a lot of perl modules and dependencies, so that when it finished, it is now 135 directories/perl modules in /root/.cpan/build
But all I needed was the 4 perl modules I first installed.
So, should I be worried about this? Was this not the correct way to make sure cpan and cpan modules was up to date? I feel somewhat bad about what just happen, when it installed over 100 modules when I only wanted to upgrade/make sure it was newest versions. Feel confused to!
Last edited: