# extensions status, to move to pecl or to drop

- Thread: https://externals.io/message/38258
- Original archive: https://news-web.php.net/php.internals/38258
- Started by Jani Taskinen on 2008-06-15T16:51:22+00:00
- Messages: 1
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #38258 — Jani Taskinen — 2008-06-15T16:51:22+00:00

URL: https://externals.io/message/38258#38258

Philip Olson [philip@roshambo.org] kirjoitti: 
> > […]
> 
> 
> 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].

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..