Re: Something about PEAR policy
| From: | Jon Parise | Date: | Sat, 21 Jul 2001 18:56:33 +0000 |
| Subject: | Re: Something about PEAR policy | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-921@lists.php.net to get a copy of this message | ||
On Sat, Jul 21, 2001 at 08:51:46PM +0200, Bjrn Schotte wrote:
> Personally, I would like to see PHPLIB's Template, Auth
> and DB class migrating into PEAR. So what's the point
> against PEARifying these classes and integrating them
> into PEAR? This is, I think, the point of the whole
> discussion. (Correct me, please, if I miss the point.)
I don't think anyone is objecting to the inclusion of PEAR-ified
PHPLIB components. The only outstanding issue is for someone to
actually do the work (i.e. convert them to the established PEAR
standards).
I believe the original "problem" (at least, from my viewpoint)
was that some people wanted to import PHPLIB wholesale (without
conversion) into the PEAR cvs tree. I argued for their
separation into individual components (e.g. 'template', 'auth'),
but, once again, no one has done to work.
--
Jon Parise (jon@csh.rit.edu) . Rochester Inst. of Technology
http://www.csh.rit.edu/~jon/ : Computer Science House
Member