Re: Re: cvs: php4 / TODO-4.1.txt
| From: | (Stig Sæther Bakken) | Date: | Fri, 20 Apr 2001 08:10:17 +0000 |
| Subject: | Re: Re: cvs: php4 / TODO-4.1.txt | ||
| References: | 1 2 3 4 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-52036@lists.php.net to get a copy of this message | ||
[Andi Gutmans <andi@zend.com>]
> At 08:13 AM 4/19/2001 -0400, Stig Sæther Bakken wrote:
> >
> >To be quite blunt, I don't have the time to implement this in C.
> >
> >I've tried to get people involved in the strategy for PEAR for months
> >and months. It's typical that nobody reacts until after
> >implementation has started though. I want to get this system up and
> >running sooner rather than later, so I'm willing to make something
> >that we throw away and reimplement rather than to not have something
> >for one more year.
>
> I think you are right.
> BTW, how are you planning on making it as transparent as possible for
> a user who downloads PHP and wants to compile it with PEAR
> C-extensions such as XML, MySQL & Oracle (these are just examples, it
> doesn't reflect my opinion if these should stay in or out of the php
> tree itself)?
Well, if all the extensions that are moved out are moved to a similar
structure in the pear CVS module: php4/ext/hyperwave ->
pear/ext/hyperwave, it should only be a matter of copying some files
and running autoconf before configure. For this we'd need a shell
script, C program or similar though. I'm in favor of a shell script,
maybe with some C helpers if it turns out to be a problem finding
lynx, wget or something similar on people's systems.
- Stig
--
Stig Sæther Bakken <ssb@fast.no>
Fast Search & Transfer ASA, Trondheim, Norway