On Sat, 2002-05-25 at 19:03, Andi Gutmans wrote: > At 09:52 25/05/2002 -0700, Rasmus Lerdorf wrote: > >This stuff is in the works. The current pear tool only works with > >php-based pear packages, but it will soon get a wrapper that will phpize > >and build extensions for you with proper dependency checking. > > Great, but I'd still like to have a KISS mechanism for C extensions like I > mentioned which would work without phpize but copy to ext/ and then do a > buildconf. I see this as the mechanism which would allow us to move certain > extensions out of ext/. > I've mentioned this to Stig in the past so he might have it on his TODO.
There are two "KISS" perspectives here, consider these two "user stories": 1. The user is about to install PHP from source, and wants to include xyzzy support, which is in PECL only. He would then have to import the xyzzy sources into his source tree and re-run autoconf and autoheader: $ pear import-source xyzzy $ autoconf $ autoheader The rest is plain configure routine. 2. The user has already installed PHP, but needs to upgrade his xyzzy extension. However, the PHP version that bundles the xyzzy he needs introduces a non-BC feature in another bundled extension, so the user doesn't want to upgrade PHP itself. However, since he build PHP with xyzzy as a shared extension, he can upgrade it easily: $ pear upgrade xyzzy This downloads the source, runs phpize, runs configure (possibly prompting for options), and replaces the old xyzzy.so file. There's not much left in the infrastructure to get there. The package.xml format needs to be able to tell which configure options to check for, and the PEAR_Config class needs to be able to store this for each extension, and finally some code doing "phpize/configure/make/make install". - Stig -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
