[Nagiosplug-devel] RFC: Plugins config file (final proposal)

[Gavin Carr]

Hey Sean,

On Fri, Feb 09, 2007 at 01:10:53AM +0100, sean finney wrote:
> On Fri, 2007-02-09 at 10:09 +1100, Gavin Carr wrote:
> > > I'm not too fussed about location. ${config-prefix}/nagios-plugins/ 
> > > plugins.ini sounds as good as any.
> > 
> > What are some typical ${config-prefix}-es? i.e. what would a full-path
> > look like?
> 
> $config_prefix is autoconf-speak for $prefix/etc.  for prepackaged
> distros that'd probably be straight /etc, and for those who do
> configure --prefix=/usr/local it'd be /usr/local/etc.

Ah okay, thanks. So you'd prefer a separate $config_prefix/nagios-plugins
directory to re-using $config_prefix/nagios? I wonder if to users the two
projects are so interlinked that two directories is confusing? I kind of 
prefer $config_prefix/nagios/plugins/plugins.ini, or even just
$config_prefix/nagios/plugins.ini (perhaps anything starting with plugins*
could be reserved?) ...

> > And as an aside, how do I source ${config-prefix} on the perl side?
> 
> it would be built-in at build time.  if you were building from the
> nagios tarball you could just use autofoo substitutions, but if it's
> being done outside i'd probably just deafult to whatever the ./configure
> script would default to (one of the two directories i mentioned
> above, i forget which).  and of course provide a way to override it
> at build time as well.

The issue with Nagios::Plugin is that it's distributed via CPAN as well 
as (?) via tarball/packages i.e. it won't necessarily be installed at
regular 'build time'. So it probably needs to be a run-time thing for 
N::P - is $config-prefix available anywhere post-install at the moment?

Cheers,
Gavin