No, just a handful of CPAN modules. Catalyst has such a large dependency tree that it's likely modules I install and Catalyst or Opsview itself will have common dependencies. If I'm installing them from repositories or CPAN, those dependencies would of course be installed with the module I want due to neither of those tools aware of Opsview's /lib/, resulting in potentially different versions in @INC and in Opsview's /lib/.
The only reason I mentioned Catalyst is that I'm pretty certain I saw somewhere opsview-web was a Catalyst app. If I'm wrong, ignore it, and just s/Catalyst/Opsview/. I'm aware of xs recompilation issues and certainly will not be going to 5.10 or 5.12 until Opsview explitly supports it. -Matt -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Ton Voon Sent: Tuesday, June 29, 2010 3:17 AM To: Opsview Users Subject: Re: [opsview-users] Installing additional perl modules onto theOpsview system On 28 Jun 2010, at 23:06, Matt Rose wrote: > > Does anyone have best practice guidelines for installing additional > perl > modules onto an opsview server either via package distribution, > cpan, or > directly insering .pm files into the @INC path? As Opsview is Catalyst > based, which has 100-150 deps last time I checked, there's a large > cross-section of essential modules that are going to be updated in the > system @INC. Is Opsview coded at all levels using its own library so > there's no chance of overriding things? > > I'd use local::lib, however with the scripts being installed being > check_whatever nagios scripts, I'd have to define local::lib for the > nagios user which could potentially cause issues for Opsview/nagios as > well. > > Or am I overthinking this and it's safe to go hog wild with module > installation? We install perl modules in there based on what Opsview needs, or if system supplied ones are downlevel to what we need. The perl modules that we deliver with Opsview go into /usr/local/ nagios/perl/lib. You can install there if you wish, but be aware that (1) we test using the specific files in there, so if you have different versions, then you're on your own!, (2) on an Opsview upgrade, the perl modules will get overwritten (which maybe downgraded or upgraded). You can usually upgrade system level perl modules without issue. There will probably be an issue if you upgrade perl to a major release though, as there are some modules which are compiled against a specific version of perl. You can install additional perl modules under a different location and make sure your @INC has your own area before /usr/local/nagios/perl/ lib to guarantee picking up your libraries first. What do you need the libraries for? You imply you are trying to setup Catalyst? Ton _______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users _______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
