Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:38258
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain sci.fi from 195.197.172.116 cause and error)
Date: Sun, 15 Jun 2008 19:51:22 +0300 (EEST)
To: Philip Olson <philip@roshambo.org>
Cc: internals <internals@lists.php.net>
Message-ID: <23347000.99091213548682740.JavaMail.jani.taskinen@sci.fi>
MIME-Version: 1.0
Content-Type: text/plain; Charset=iso-8859-15; Format=Flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] extensions status, to move to pecl or to drop
From: jani.taskinen@sci.fi (Jani Taskinen)

Philip Olson [philip@roshambo.org] kirjoitti: 
> >
> >> / 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).
> >
> > 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].

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..