Re: extensions status, to move to pecl or to drop
| From: | Timm Friebe | Date: | Sun, 15 Jun 2008 09:05:40 +0000 |
| Subject: | Re: extensions status, to move to pecl or to drop | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-38243@lists.php.net to get a copy of this message | ||
Hi,
Can be moved PECL - interbase - fpdf - fbsql - sybase and sybase_ctSybase can be moved, it is unmaintained. I would've done this long ago if I could, karma-wise. Sybase_ct works perfectly for us at 1&1 and despite feature requests that exist and me not having put big efforts into it over the past years it serves millions of requests a day without problems. The next big step would be to add all the
if (unicode)-stuff needed for PHP6 and/or to port it to a PDO driver, which I frankly don't have time to do.
If an extension is moved to PECL, it is a bit more of a hassle to install it: Windows: instead of enabling it in php.ini you need to download the dll (not sure who builds that? Is it done automatically?) / 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). Plus I'm not sure how developing works, would you mess up your PHP checkout tree by copying the pecl/ext/XXX to php-src/ext/XXX and the running all these magic autotools? Correct me if I'm wrong here, but I guess that's what people on both sides - extension developers and PHP users - are afraid of when you announce PECL-moves, right? Before you say "PECL is not siberia" think about the following: If PECL moves wouldn't hurt the user experience for any partys involved, why would any extension live in php-src/ext/?
- Timm