Re: Default extensions (was: mbstring)

Best regards Andrey Hristov ----- Original Message ----- From: "James Cox" <imajes@php.net> To: "Jani Taskinen" <sniper@iki.fi>; "Jon Parise" <jon@php.net> Cc: "PHP Development Mailing list" <php-dev@lists.php.net> Sent: Tuesday, September 03, 2002 12:19 AM Subject: RE: [PHP-DEV] Default extensions (was: mbstring) > > > 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? > > > > i'm +1 for that if it means that first it disables everything, and then you > enable stuff bit by bit... --disable-all is good for me for one reason - to speed dev builds. When I work on arrays I don't want to link xml, mysql and so on. I've disabled them in config.nice but --disable-all is better because it won't be needed to search which modules I can disable. --disable-all can be good for some sysadmins that run large websites and want to have only that they need - disabling all and adding what is needed thus decreasing the size of the binary. The idea about ncurses based setup is very good and I hope "we" will found the man/men who will do it. On the other hand it won't be good if mysql is disabled by default. I saw one reason here : endless bug reports about mysql_connect() more than these about Apache2 builds. Another reason : mysql is easy to install on most platforms (mostly windows) and because PHP is easy to learn (good curve) - PHP is the choice as the language to write scripts. Also I think that enabling postgresql support by default will be good. Thus we will provide support not only for one database in the builds. Mysql is overpromoted and PG stays in the dark (this is my opinion). Regards, Andrey