Sterling has a good point that sqlite is something that could really boost
PHP. Currently, the only way to ensure that it is a standard feature is to
enable it by default. Sad but true.
That is true. It's something of a chicken and egg problem. I think the reason that people don't use non-stock configurations is that largely the kitchen sink is enabled in PHP. The less this is true, the more folks will have to consider how they want to build it.
Perhaps a '--enable-shared=all' (like apache) or '--enable-hosting' or some such that builds the kitchen sink in.
My main misgiving with it being enabled by default is that it will make it
harder for me to publish releases of the extension between releases of PHP.
Right. Being able to do this easily is a Good Thing (imho).
For the reasons that Sterling has suggested, I'd like to see the sqlite recommended as a default (but don't mind if it isn't).
I dig including it in ext, and bundling the full sqlite sources as well. I just don't think it should be enabled by default.
George
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
