On Wed, Sep 28, 2011 at 9:33 AM, jcbollinger <[email protected]> wrote: > > On Sep 27, 11:13 am, Aaron Grewell <[email protected]> wrote: >> We're not using CPAN. Modules are installed as RPMs in our environment. > > As it should be on an RPM-based distro.
Yes, I wish it could be so... Unfortunately the one system that I need this for is running cPanel on a CentOS 5 system. cPanel installs its own custom Perl (as well as many other packages, including Ruby so I have to install Puppet and Facter via GEM rather than RPMs). I'm trying to get munin installed on this system so that I can monitor the system. Since cPanel installed a custom Perl the CentOS Perl module RPMs won't install. > I strongly recommend installing software only via the system's native > package manager. If you violate that by installing Perl itself some > other way (e.g. manually), then anything goes for that Perl > installation (or Ruby, Python, ...), but if you are using the system's > Perl then you should use the system's Perl packages. If you need Perl > modules not available pre-packaged then package them yourself; it's > not that hard, especially if they are already available from CPAN. > > Doing otherwise introduces a significant risk of incompatibilities > arising and even your Perl modules being mangled, plus it makes > management more than twice as hard. I totally agree, but since I can't get rid of cPanel and I don't want to go to the trouble of building RPMs for just one system I'm kinda stuck doing it the "wrong" way. -- Jeff Ollie -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
