Re: split of PEAR into PEAR and PEAR_Developer

Yes, by implemeting it in C.  PEAR_Developer will only contain "pear" 
sub-commands needed only by developers ("pear package" etc.) 

 - Stig

On Tue, 24 Aug 2004, Norbert Mocsnik wrote:

> Hi,
> 
> Sounds cool. Will this have any effect on the PEAR class itself?
> Any chances on decreasing the filesize of PEAR.php in the future?
> 
> Regards,
> Norbert
> 
> Greg Beaver wrote:
> > Hi,
> > 
> > Soon, I would like to split PEAR into two distinct packages, one 
> > designed for those who wish to simply install and uninstall packages, 
> > and another for those who wish to actually package them up.
> > 
> > Any concerns about calling the subpackage PEAR_Developer?  It would 
> > force all of the development code to move into the Developer 
> > subdirectory, breaking BC, so this would be for PEAR 2.0, most likely.
> > 
> > Greg
> 
> 

-- 
PEAR Core List Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php