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? -Matt _______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
