Unfortunately we don't live in a perfect world where
sysadmins know how to read and listen to their users
requests. That's why mysql for example is enabled by default.
(or that's the main reasoning behind it at least)
And we can't educate people or force them to anything either.
Maybe we should add a general '--disable-all' option?
--Jani
p.s. I'm +1 for making everything not enabled by default..
--
On Mon, 2 Sep 2002, Jon Parise wrote:
>On Mon, Sep 02, 2002 at 03:52:50PM -0400, Dan Kalowsky wrote:
>
>> > If we should reduce number of modules built by default, 1st
>> > module should be MySQL. Removing MySQL does not cause any
>> > technical problems at all.
>>
>> I'll agree to that as well. +1 on removing --with-mysql as a default.
>> Although realize I'm also +1 on removing any default modules that are not
>> essential to PHP's running.
>
>After some thought, I think I agree with this (disable by default)
>approach, as well. For instance, if you want just PostgreSQL support,
>you not only have to --with-pgsql but also --disable-mysql[*].
>
>I don't think there's any harm in asking MySQL users to --enable-mysql
>support if that's why they want, even if it is purportedly the most
>popular RDBMS with PHP. Chances are that those same users will likely
>need to set at least one other ./configure option, anyway.
>
>It's much easier, conceptually, to tell PHP users that "everything is
>off by default" than "look at the './configure --help' output" to
>figure out if you need to explicitly enable (or disable) something.
>
>Of course, I'm making general claims without providing any kind of
>reliable figures here. Perhaps it would be interesting to conduct
>some kind of anonymous PHP extension survey to see how many people
>configure / use which modules.
>
>[*] Not that MySQL support harms anything, but why compile something
> you're not going to use?
>
>
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
