[Nagiosplug-devel] How would upgrading autoconf & automake go down?

[Ton Voon]

One great thing about the 1.4 release is that check_disk uses the 
coreutils libraries to get filesystem information. This is great 
because we get to hook into GNU's code and thus get all their fixes and 
support for lots of different OSes.

So, I've been working on trying to make it more clear which are 
coreutil files and which are not. The aim is to simulate what GNU are 
doing and thus make it easier to upgrade when they release a new 
version of coreutils.

This took me much longer than I expected, but now I've got a working 
version on my dev box. These are the changes:

- Moves m4 files into m4 directory
- Move coreutil checks out of configure.in into np_coreutils.m4 file 
and calling coreutil m4 checks
- Use a libcoreutils.a library file for coreutil stuff, keeping 
libnagiosplug.a for nagios plugin shared code
- Fixes a compile issue on MacOSX with already defined declarations in 
fsusage.c
- Compile extra files that may be required on non-GNU systems
- Fixes the "automatically discovered file `fsusage.c' should not be 
explicitly mentioned" message when running autoconf

However, one thing I've noticed is that I get errors with autoconf 
v2.57, so this means the dependency is now on autoconf v2.58. Also, I 
am using automake v1.6.3 while the automake dependency is v1.6 in the 
dev guidelines - I haven't installed the older version to test.

Before I commit, I wanted some opinions - is it worth making these 
changes and force us using newer GNU tools?

Ton