Re: [Fink-devel] Porting Nagios (was netsaint) and doing itright...

[Max Horn]

At 8:11 Uhr +0100 06.02.2003, David wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Hello peeps.



Nagios (which was Netsaint) will be my first largish package and I
would like to know, how I should go about doing this properly. There
are a number of issues.





a) The configure script needs to be created using autoconf prior to
running it or it wont recognise the gd libraries properly. Do I do this
in a compile script ala:   autoconf; configure; make?

The best way is to go and kick the upstream maintainers butt to get serious and include a configure script as everybody else does (autogen.sh should be only used by the people developing this stuff; avarage joe user might not even have automake etc. installed).

b) Nagios has numerous backends you can use for data storage. Mysql,
postgresql or text files could be used. I was talking to Justin the
other night since he asked who was porting Nagios and from his
suggestion I think it would be proper procedure to make something like



	nagios-mysql

	nagios-postgresql

	nagios-text

Aye. Of course it would be nice if the backends where plugins, then you could just build them all and put them into splitoffs, but I guess that's no option.

c) There is an embedded Perl interpreter within Nagios, you can either
enable or disable it at compile time. It does make the whole software a
lot more versatile when it is being enabled at compile time, however,
should I simply enable this in all packages or make a package which is
then called

	nagios-mysql-embeddedPerl

	nagios-postgresql-embe.....  and so on?

If you want to do it, that's the way to go. Of course then you have 6 packages already.

I somehow seem to remember, that we do enable everything as far as that
is possible. Correct?

If sanely possible, yes... If you decide not to enable something, then make sure it's really disabled (e.g. some package activate features in their configure scripts only when some other package is found by them, so if you want that feature to be never enabled, it's not sufficient to hope that other package is not installed; rather you need to tell the package to never use that extension).


Max


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel