# Moving to PECL

- Thread: https://externals.io/message/2207
- Original archive: https://news-web.php.net/php.internals/2207
- Started by Sterling Hughes on 2003-06-07T17:15:23+00:00
- Messages: 5
- 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

---

## #2207 — Sterling Hughes — 2003-06-07T17:15:23+00:00

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

Hi,

So now that the PEAR framework for bundling extensions is in place, I
figured I'd start a thread about moving all extensions to PECL, and then
selectively bundling them from PECL (perhaps maintaining physical
aliases as well.)

With the new system, when a release is made, the RM simply needs to run
::

./bundle-release 

In the PHP5 directory.  And the packages are bundled at the last stable
version.  I'm for moving on getting this done asap.  So I guess the
discussion now is:

a) Any last objections?
b) Should any extensions fall within the PHP-QA process?
c) Is there anything I'm missing/that is missing at this point? 

-Sterling
-- 
"I can't give you a brain, so I'll give you a diploma"  
    - The Great Oz, The Wizard of Oz

---

## #2208 — James Cox — 2003-06-07T17:23:06+00:00

URL: https://externals.io/message/2207#2208 · In reply to: #2207

> 
> So now that the PEAR framework for bundling extensions is in 
> place, I figured I'd start a thread about moving all 
> extensions to PECL, and then selectively bundling them from 
> PECL (perhaps maintaining physical aliases as well.)
> 

I'm +1 on this.. And already offered to move stuff, so one other point on
Sterling's list is extensions that will move, and extensions that will stay
firmly where they are.

 -- james

---

## #2211 — Shane Caraveo — 2003-06-07T18:23:36+00:00

URL: https://externals.io/message/2207#2211

Marcus Börger wrote:
> 
> 
> Some extensions like mbstring behave different when not builtin. So
> i suggest we find out which theses are and let them in.

Having them in pecl in no way prevents them from being compiled builtin.

> Also for extensions like ext/gd i don't see any reason to move them
> out of the php main tree.

Release cycles and QA, which is the only reason to do any of this at all.

Shane

---

## #2212 — Edin Kadribasic — 2003-06-07T23:22:02+00:00

URL: https://externals.io/message/2207#2212 · In reply to: #2207

> Hi,
> 
> So now that the PEAR framework for bundling extensions is in place, I
> figured I'd start a thread about moving all extensions to PECL, and then
> selectively bundling them from PECL (perhaps maintaining physical
> aliases as well.)

-1
I'm strongly against this move. First of all PEAR framework for handling 
extensions is nowhere near complete. It has no support for Windows. It has 
no notion of what version of PECL package can be built with what version 
of PHP. It requires latest and the greatest GNU tools installed on the 
system which is rarely true for some commercial Unixes.

If we are going to bundle most of those extensions anyway, removing them 
to PECL would directly reduce the quality of the release as most of them 
will receive very little testing.

I understand the wish to make the release process more easy, but I'm 
afraid that this proposal will achieve exactly to opposite effect. It will 
certainly make maintenance of the Windows binary releases much more 
difficult.

Edin

---

## #2214 — Alan Knowles — 2003-06-08T02:53:01+00:00

URL: https://externals.io/message/2207#2214 · In reply to: #2207

Is PECL going to move to the top level in CVS? - it's a bit hidden away 
at the moment... (and I guess after these are moved  - creating a 'real' 
php5 directory?? - so their's not so many empty directories lying around?)

Regards
Alan


Sterling Hughes wrote:
> Hi,
> 
> So now that the PEAR framework for bundling extensions is in place, I
> figured I'd start a thread about moving all extensions to PECL, and then
> selectively bundling them from PECL (perhaps maintaining physical
> aliases as well.)
> 
> With the new system, when a release is made, the RM simply needs to run
> ::
> 
> ./bundle-release 
> 
> In the PHP5 directory.  And the packages are bundled at the last stable
> version.  I'm for moving on getting this done asap.  So I guess the
> discussion now is:
> 
> a) Any last objections?
> b) Should any extensions fall within the PHP-QA process?
> c) Is there anything I'm missing/that is missing at this point? 
> 
> -Sterling


-- 
Can you help out?
Need Consulting Services or Know of a Job?
http://www.akbkhome.com