About posting 4.0.3-dev reports

Hi, Andi said in php-dev he'd like to have reports about 4.0.3-dev. - I have the feeling posts in php-qa are not as much read as they would be in php-dev. For e.g. nobody replied to my post about ia64, I thought it was a big news ! :) - Could it be feasible to create an on-line database of build success depending on the platform, the compiler, the build, the modules chosen, links to the changelog entry, etc. ? I think it could help tracking the history of modules being able to be built or working properly. For e.g. suEXEC didn't work from the 4.0 beta until 4.0.2, dBase was also broken until 4.0.2. PEAR and the regression tests are a good idea for this. Don't get me wrong, I really like the PHP development process, I'd just like to try to make it even better. One great thing would be a tinderbox feature (like Mozilla's). - I'll post 4.0.3-dev reports this week on Digital Unix, NetBSD 1.3.3 and NetBSD 1.4.2. So far, db support is fixed, but sockets support still fail compiling on Alpha with gcc 2.7.2.2, images won't display on phpinfo() with --enable-discard-path, ./buildconf won't work with native digital's make (I just saw a fix for BSD/OS), and I have trouble with curl support on one exotic system. - I didn't have any reply to one of my previous posts about internal sendmail support on Unix and/or SMTP functions through IMAP. I'll start coding SMTP support I think... -- Olivier.Cahagne@epita.fr