Re: extensions status, to move to pecl or to drop
| From: | Jani Taskinen | Date: | Sun, 15 Jun 2008 16:51:22 +0000 |
| Subject: | Re: extensions status, to move to pecl or to drop | ||
| Groups: | php.internals | ||
| Request: | Send a blank email to internals+get-38258@lists.php.net to get a copy of this message | ||
Philip Olson [philip@roshambo.org] kirjoitti:
I've toyed with idea of putting everything in PECL. Including the core, engine.. But that's utopia..it would just be so cool to just say "php --update" and it would update itself and everything needing to be updated.. ;) It shouldn't be that hard to integrate pecl stuff in configure. Just hijack the "unknown-option" code which I added some time ago and try and see if the unknown stuff can be found in PECL and do..something. I can look into this after I get back to work in a week or so..if someone else (tm) doesn't do it before that.. :D --Jani p.s. It doesn't have to just "fetch" the stuff, it can be compiled the same time as well..If the release is done correctly, a simple pecl install sybase works. And on a related note, have we considered any sort of fetch integration with configure? You know, like --with-apc would grab it much like 'pecl download apc' does today. Or more likely a trigger, like --with-apc=fetch,beta ... you get the idea. A friendlier this[1]./ Un*x: Get a .tar.gz, unpack, phpize, configure and make (last time I tried that didn't work for me, must've been some wrong auto-whatever).