R Lists06 wrote:
It is my experience that CPAN installs can or will tend to do things I do
not want it to do (or cannot control) in a RPM environment among other
things...
I use the following methods, in this order, for installing Perl modules:
1. Distro's native repository
2. Well-maintained third-party repository (rpmforge.net has a number of
RHEL4 packages through DAG's repository, including Perl modules)
3. cpan2rpm
4a. CPAN command-line
4b. Download the source and build an RPM
5. Download the source and install
If at any point the module is unavailable, too old, or cannot be
installed, I move to the next option. The idea is to have as much as
possible managed through RPM repositories (which will make installing
bugfix/security upgrades trivial), then as much as possible through RPM,
then get what's necessary.
I haven't quite settled on what order to do 4a and 4b in. 4b is better
from a management perspective, but 4a is a lot simpler to do.
--
Kelson Vibber
SpeedGate Communications <www.speed.net>
