RE: [PHP-PEAR] RFC on merge of PHPLib and Pear

From: Date: Wed, 07 Mar 2001 21:30:11 +0000
Subject: RE: [PHP-PEAR] RFC on merge of PHPLib and Pear
References: 1  Groups: php.pear 
Request: Send a blank email to php-pear+get-1690@lists.php.net to get a copy of this message
> -----Original Message----- > From: Jon Parise [mailto:jon@csh.rit.edu] > Sent: Wednesday, March 07, 2001 12:28 PM > To: php-pear@lists.php.net > Subject: Re: [PHP-PEAR] RFC on merge of PHPLib and Pear > > > On Wed, Mar 07, 2001 at 12:20:10PM -0500, Jeffrey A. Stuart wrote: > [...text deleted...] > > I'm just afraid that people will start viewing PEAR as a large > collection of classes in varying stages of development. There is also > the danger of users writing code that references the classes in > PEAR/PHPLIB/, which (as I understand it) will only be their temporary > location. > Ok... valid point... maybe some of this doesn't have to happen in the Pear/PHP Repository... :) > As a side issue (and I've mentioned this before), PEAR really should > have its own source repository. I don't really like the idea of PEAR > being distributed with the PHP releases. > That's a GREAT point... what do we have to do to move pear into it's on repository? [...text deleted...] > > Chuck and I just happen to agree on a lot of project management and > engineering points. We're also pretty vocal about them. For the most > part, my opinions, at least, are based on years of experience with the > Horde project (both coding and support). That's fine... don't get me wrong, I'm GLAD that people are commenting... :) You're coming up with things that I hadn't thought of. :) Which in the end is WHY I posted this email. :) -- Jeff Stuart jstuart@neo.rr.com

« previous php.pear (#1690) next »