Re: [PHP-DEV] Could some kind soul review these patches please. From: Peter Bowen (pzb <email protected>)
Date: 12/13/00

I agree with Andi. I think it is time to see PEAR start to get
extensions that are not critical to the basic functionality of PHP itself.
I think that it is important that several things get done before this
happens:

1) We need to stabilize and version the extension API. I have heard
concerns on this list about the versioning problem before, but don't think
it ever got resolved. Zend extensions, such as the optimizer, have an
interface API number, but we haven't implemented this for PHP extensions,
AFAIK. Additionally, in order for an extension repository to be
sucessful, compiled extensions must be available, at least for Win32. We
don't want to make people upgrade all their extensions every time a point
release of PHP comes out.

2) We need to try to fix the dl() problem with threading. dl() is an
important to the concept of PEAR. In Perl, CPAN would not work if we
could not use the module at runtime, on a per script basis, and I think
that the same is true for PEAR. I'm not sure if dl() is possible in a
threaded environment, but I hope so.

3) We need to define what is core functionality of PHP, and move the rest
of the existing extension to PEAR. Obviously, standard is a basic
requirement for PHP to operate, and I would suggest that most of the
others could be moved to PEAR, if the dl() problem is fixed.

4) We need to define how we will handle documentation. We will have to
move the appropriate docbook manual pages to each extension, and build a
system to automatically compile them to a readable format. It would also
be desirable to have them all available on pear.php.net.

I would encourage developers, and users, to comment on the above. I, too,
would be happy to do part of the work necessary to make a PEAR C
extension repository a reality.

Thanks.
Peter

On Wed, 13 Dec 2000, Andi Gutmans wrote:

> I personally don't think this is a great thing to have but if some people
> find it useful it could be added (off by default IMO especially because of
> ISPS).
> We should really work on the PEAR C extension repository which would allow
> us not to include every extension in the main package but on an easily
> accessible site. It would have to be very easy to use of course. But I'm
> probably stating the obvious here :)
> Why don't we discuss what we want this repository to look like and once we
> agree we can try and find who will implement it. I'll be happy to do part
> of it.
>
> Andi
>
> At 10:06 PM 12/12/00 -0700, Ron Chmara wrote:
>
>
> >Sam Liddicott wrote:
> > >
> > > Maybe this patch meets approval.
> > >
> >Is this still pending? Lost in the noise of XML and OO?
> >:-)
> >
> >-Ronabop
> >
> >--
> >Personal: ron <email protected>, 520-326-6109, http://www.opus1.com/ron/
> >Work: rchmara <email protected>, 520-546-8993, http://www.pnsinc.com/
> >The opinions expressed in this email are not neccesarrily those of myself,
> >my employers, or any of the other little voices in my head.
> >
> >--
> >PHP Development Mailing List <http://www.php.net/>
> >To unsubscribe, e-mail: php-dev-unsubscribe <email protected>
> >For additional commands, e-mail: php-dev-help <email protected>
> >To contact the list administrators, e-mail: php-list-admin <email protected>
>
> ---
> Andi Gutmans <andi <email protected>>
> http://www.zend.com/
>
> 

-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: php-dev-unsubscribe <email protected>
For additional commands, e-mail: php-dev-help <email protected>
To contact the list administrators, e-mail: php-list-admin <email protected>