# moving extensions to pecl

- Thread: https://externals.io/message/17510
- Original archive: https://news-web.php.net/php.internals/17510
- Started by Marc Boeren on 2005-08-03T14:01:08+00:00
- Messages: 2
- 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

---

## #17510 — Marc Boeren — 2005-08-03T14:01:08+00:00

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

Hiyall, 

A while back ext/dbx and ext/ircg were 'moved to pecl' (without any
discussion, but that's not the point).
However, there are no packages on pecl for either extension, which might
lead people to believe that a 'move to pecl' is more like a 'remove from
php' action. Should it not be policy to require the necessary packaging
for pecl _before_ the source is moved in cvs?

Ciao, Marc.

---

## #17515 — Wez Furlong — 2005-08-03T19:00:46+00:00

URL: https://externals.io/message/17510#17515 · In reply to: #17510

In general, unless the extension is a really ancient forgotten thing,
the person moving it should coordinate with the current maintainer to
set that up.

Would you mind creating the appropriate package.xml file and tarball
and releasing dbx via PECL, Marc?

Let me know if you need an account for the PECL site.

--Wez.


> 
> Hiyall,
> 
> A while back ext/dbx and ext/ircg were 'moved to pecl' (without any
> discussion, but that's not the point).
> However, there are no packages on pecl for either extension, which might
> lead people to believe that a 'move to pecl' is more like a 'remove from
> php' action. Should it not be policy to require the necessary packaging
> for pecl _before_ the source is moved in cvs?
> 
> Ciao, Marc.