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.
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.