Brad,
In any case, we are in a complete feature freeze right now. I sent an email
about this to [EMAIL PROTECTED] Only bug fixes allowed. Please #if BRAD_0 that
code in HEAD. I don't see a problem allowing the addition of such simple
wrapper functions after 5.1.0 goes out the door; but I don't want such code
changes at this point.
Andi
At 12:54 AM 7/19/2005 +0400, Antony Dovgal wrote:
On Mon, 18 Jul 2005 16:34:44 -0400
Brad House <[EMAIL PROTECTED]> wrote:
> Perhaps. There was discussion once upon a time along those lines,
> but nothing else came of it. I'd have to know what it entails,
> and if it would prohibit the extension from being distributed
> with the main PHP codebase.
AFAIK the general plan is to move almost all extensions to PECL
(and we're working on it, take a look on how many extensions were moved
there in 5.0 and 5.1), so users would be able to get & install only
extensions they really need.
Personally I don't think that ext/mcve is used by large number of users
(I haven't ever heard of someone using it) and IMO that's a perfect reason
to move it from the core to PECL.
I can be wrong, though.
There are also several rather important reasons to do so:
1) you wouldn't depend on PHP release cycles.
2) you would be able to use PECL infrastructure to build Win32 *.dll's
3) Others.
All this doesn't mean that users will not be able to install/use the
extension
or even have some problems with it. Extensions from PECL can be installed
with this command:
# pear install extname
See details here: http://www.php.net/manual/en/install.pecl.php
> Forgive my ignorance, but I have
> not even looked into what PECL really is.
Well, I'd recommend to take a look on it, since you're the maintainer of
an extension..
--
Wbr,
Antony Dovgal
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
