Re: [phplib] [Fwd: [PHP-PEAR] Merging PHPLIB into PEAR] From: Kristian Koehntopp (kris <email protected>)
Date: 01/18/01

In netuse.lists.phplib you write:
>Does anyone know what the implications of this are going to be?
>I've never used PEAR and my fear of the unknown is kicking in.
>Will this break existing PHPLib code? Is there anything we can
>do now to better prepare our code for this sacred union?

PHPLIB code will in part be 1:1 imported into a different
repository, no problem here. Other parts of PHPLIB code will
have to merge with existing PEAR code with similar
functionality. Here it is my wish that there exist 1:1 wrapper
classes in order to make existing code runnable with PEAR.

PEAR is part of the normal PHP compile and install process, and
it will have much better availability that PHPLIB in hosting
environments. Also, it has a much more active development
process than PHPLIB has had in the last 12 months.

PEAR strives to become the CPAN of PHP. It may be unknown at the
moment, but it won't stay that way.

Kristian

---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-unsubscribe <email protected>
For additional commands, e-mail: phplib-help <email protected>