Re: Windows installer

Hi folks I got no response to the message I sent the other day (included again below). Maybe people are busy, or aren't using the dlls? If anyone can give me any info, please do - if not, I'll post the question to the php-win list tomorrow. Cheers -- Phil Driscoll Dial Solutions +44 (0)113 294 5112 http://www.dialsolutions.com http://www.dtonline.org -----Original Message----- From: Phil Driscoll <phil@dialsolutions.co.uk> To: php qa <php-qa@lists.php.net> Date: Tuesday, September 12, 2000 10:56 AM Subject: [PHP-QA] Windows installer >Hi folks > >I'm once again in a position to devote some time to the windows installation >program. > >I need to know what extension modules we can safely ship with the standard >release. >The good guys at php4win.de have made available the following: > >bcmath (built-in) >calendar >com (built-in) >cpdf >cybercash >db >dbase >domxml >exif >fdf >ftp >gd >gettext >ifx (informix) >imap >interbase >java >ldap >mssql65 >mssql70 >mysql (built-in) >oci8 >odbc (built-in) >pcre (built-in) >pdf >pgsql >session (built-in) >sybase_ct >wddx (built-in) >xml (built-in) >zlib > >as well as new: >dotnet (.net experimental!) >mhash >oracle >sablot (sablotron xslt) >crypt() (native support for the crypt function) > >Clearly, the built in extensions are shippable ;-) however is this true for >the others, or does their existence in the list just mean that they have >been successfully built? > >We should only ship tested modules, so could people let me know which >modules work ok, and also if there are any sections in php.ini which need to >be filled in with anything other than the defaults in php.ini-dist if the >module is included. > >Thanks >--