Hi All!

Not quite a week later, there is the 2nd release candidate for the upcoming ngIRCd release 17 available for downloading and testing. The changes since -rc1 are:

* doc/Makefile.am: don¹t set docdir, automake handles it already * Only use "__attribute__ ((unused))" if GCC >=2.8 is used * Only try to set FD_CLOEXEC if this flag is defined * Added m68k/apple/aux3.0.1 (gcc 2.7.2) to doc/Platforms.txt * Don't use PARAMS() macro for function implementations * ./configure: check support for C prototypes again * ./configure: check if C compiler can compile ISO Standard C * Make sourcecode compatible with ansi2knr again * Generate ngIRCd version number from GIT tag * ZeroConf: include header files missing since commit a988bbc86a * New doc/HowToRelease.txt file describing the release process * Updated contrib/platformtest.sh (new version scheme)

So the biggest change is that really old compilers (pre-ANSI) are supported again; this has been tested on ancient Apple UNIX (A/UX) 3.0.

If you want to test ngIRCd yourself, you can use the sequenze

tar xzf ngircd-17~rc2.tar.gz cd ngircd-17~rc2 contrib/platformtest.sh

which will (hopefully) result in a nice summary after compiling the daemon and running the test suite.

The release candidate is available for downloading and testing at the usual locations:

ftp://ftp.berlios.de/pub/ngircd/ngircd-17~rc2.tar.gz ftp://ngircd.barton.de/pub/ngircd/ngircd-17~rc2.tar.gz

The GnuPG signatures for 17~rc2 and patches from release 17~rc1 are available as well and can be downloaded from here:

ftp://ngircd.barton.de/pub/ngircd/ ftp://ftp.berlios.de/pub/ngircd/

You can have a look at the complete history and every single patch using the GIT web-frontend located at:

http://ngircd.barton.de/cgi-bin/gitweb.cgi?p=ngircd.git

Please test this release candidate thoroughly and report all bugs and problems you encounter using the bug tracker (http://ngircd.barton.de/bugzilla/index.cgi) and/or this mailing list.

I think I'll update my Debian packages with this release candidate as well as build a new Mac OS X package, so that this code gets even more testing. What do you think?

Regards Alex