Re: Moving to PECL
| From: | Tomas V.V.Cox | Date: | Sat, 14 Jun 2003 16:21:12 +0000 |
| Subject: | Re: Moving to PECL | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-2331@lists.php.net to get a copy of this message | ||
"Georg Richter" <georg@php.net> escribió en el mensaje
news:19QrJS-1tt1xQ0@fmrl00.sul.t-online.com...
> On Sunday 08 June 2003 18:23, Rasmus Lerdorf wrote:
> > The one point on the QA issue is that nobody ever looks through all the
> > PECL extensions, but we occasionally grep through all the ext/*
extensions
> > to make sure that an API change, or just a simple mistake that we found
> > does not occur in other extensions.
> >
> > We need to raise the priority of PECL/* in the hearts and minds of the
> > developers so that instead of just scanning ext/* we also scan PECL/*.
> > Getting it out of PEAR and up to its own top-level cvs module is a
start.
> > It really doesn't have anything to do with PEAR and needs to be a lot
> > closer to the php-dev crowd than the pear-dev crowd.
>
> +1
>
> For everyone, developers and users this would be a clear scheme.
> Easy to find the stuff you need. As Rasmus said, PEAR and PECL are
diffrent
> things and should be separated.
>
Btw, would be nice if some php-developers get involved in the pecl extension
managment of the pear installer as they know pretty much about the real
needs for them. I could write a quick "PEAR installer" doc or answer dubts
about the implementation.
Tomas V.V.Cox