RE: [PEAR-DEV] Misunderstanding on what PEAR is
| From: | Dietrich Ayala | Date: | Sun, 11 Nov 2001 18:45:00 +0000 |
| Subject: | RE: [PEAR-DEV] Misunderstanding on what PEAR is | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-2813@lists.php.net to get a copy of this message | ||
You may not see the need, but from the input on the list it would seem that
many users/developers have the need for a CPAN-like repository, a more
flexible PEAR.
It also seems that they are not insisting on the watering-down of PEAR as
you describe it, but are proposing a *separate* repository.
Perhaps it can be created and called something else, if the PEAR developers
don't want it to be part of PEAR?
> -----Original Message-----
> From: cox@idecnet.com [mailto:cox@idecnet.com]
> Sent: Sunday, November 11, 2001 12:43 PM
> To: PEAR DEV
> Subject: [PEAR-DEV] Misunderstanding on what PEAR is
>
>
> The PEAR concept it self is only a Repository, a unique web repository
> and the works done in this area (pear web and pear installer/packager)
> are in this direction. Also it's not a common repository, is a
> repository with software that:
>
> * has been approved to be in by the Pear developers and has the general
> concensus of the Pear community (Pear users)
> * follows a unique coding standars (avaible to read, already stadarized
> and used in all PEAR)
> * uses a common error handling mechanism
> * tries to have a similar way of use
> * has documentation about its API in the PHPDoc format
> * has documentation/examples/tests (to be marked as stable)
>
> All this _is_ PEAR proyect. I don't see the point of splitting the Web
> Repository, changing the actual conventions or droping/adopting things
> that doesn't meet this list.
>
> About the always asked thing: "php4/pear" vs "pear" (the CVS modules).
> "php4/pear" will only contain things needed by the PEAR infrastructure
> and will be distributed with the php distribution. The "pear" module
> contains PEAR software that will be distributed via the pear web in the
> form of pear packages handled by the PEAR Package Manager (formed by the
> "pear" script and the classes inside "php4/pear/PEAR/*"). This module is
> only a tool for helping the developers who joins PEAR but its use is
> completely optional. It's better for PEAR not to be distributed with php
> because we could make releases avaible under our own cycle.
>
>
> Tomas V.V.Cox
>
> --
> PEAR Development Mailing List (http://pear.php.net/)
> To unsubscribe, e-mail: pear-dev-unsubscribe@lists.php.net
> For additional commands, e-mail: pear-dev-help@lists.php.net
> To contact the list administrators, e-mail: php-list-admin@lists.php.net
>
>