Everything
php
Learn Community Releases The PHP Project
Home » Project » Newsgroups » php.internals » Too many extensions bundled with the Windows Installer? »

Too many extensions bundled with the Windows Installer?

php.internals

Scott MacVicar

19 years ago
The Windows Installer seems to allow someone to enable just about every extension that can be built, roughly about 118. It seems that most people assume that they need every feature of PHP to work, especially thsoe in Windows. Out of those 118 extensions there are 3 which cause crashes and blank pages. SAM extension has some interesting code its its RINIT function to require a PHP file, if its not there it exits and you get a blank page with display errors off. The thread pecl extension and iisfunc don't work when and cause crashes on module shutdown. I propose that we disable all experimental extensions in the installer to prevent this, some of these extensions don't even have a release listed on http://pecl.php.net Scott

Frode E. Moe

19 years ago
On Sun, Jul 01, 2007 at 22:56:57 +0100, Scott MacVicar wrote:
> The Windows Installer seems to allow someone to enable just about every > extension that can be built, roughly about 118. It seems that most people > assume that they need every feature of PHP to work, especially thsoe in > Windows. > > I propose that we disable all experimental extensions in the installer to > prevent this, some of these extensions don't even have a release listed on > http://pecl.php.net
While we're on the topic of bundled windows extensions, is there a reason for not shipping a FreeTDS version of the MS SQL extension (aka "php_dblib.dll")? In my experience, the FreeTDS version works much better than the default php_mssql.dll one, especially for things like unicode/UTF-8 support and the NVARCHAR data type. (Especially if http://bugs.php.net/bug.php?id=41539 could be fixed :) )

Antony Dovgal

19 years ago
On 02.07.2007 01:56, Scott MacVicar wrote:
> The Windows Installer seems to allow someone to enable just about every > extension that can be built, roughly about 118. It seems that most > people assume that they need every feature of PHP to work, especially > thsoe in Windows. > > Out of those 118 extensions there are 3 which cause crashes and blank pages. > > SAM extension has some interesting code its its RINIT function to > require a PHP file, if its not there it exits and you get a blank page > with display errors off. > > The thread pecl extension and iisfunc don't work when and cause crashes > on module shutdown.
Yes, I don't see any reasons to ship extensions that were never released (and just happen to build successfully). Those people who want crashes^H^H^H^H^H^H^H to play with them can easily find the DLLs on pecl4win.php.net. In fact, I think the installer package should not include extensions which are not included in the core. Windows people are no better/worse than the others and are able to download a PECL package.
> I propose that we disable all experimental extensions in the installer > to prevent this, some of these extensions don't even have a release > listed on http://pecl.php.net
-- Wbr, Antony Dovgal

Jani Taskinen

19 years ago
On Mon, 2007-07-02 at 12:18 +0400, Antony Dovgal wrote:
> Windows people are no better/worse than the others and are able to download a PECL package.
And those who just install everything that's included in the release won't get into unexpected trouble. :) --Jani