Re: PEAR DB copied to pear/

> >I've repeated this several times, but here we go again: IMHO in order for > >PEAR to be universally accepted it must go standard class library way, not > >cpan way. Reason is simple. If I have to distribute my application that uses > >PEAR I don't want to write 10 page manual, "and then you download that class > >... ". Instead I would like to be able to assume that if there is PHP on the > >machine there is PEAR as well. > > Would you like to download a PHP distribution that contains > 9MB > of PHP code? I don't. The whole of PEAR's current repository fits into a 1MB tarball. But that's beside the point. The question is whether PEAR wants to become what LIBC is to C, STL to C++, or what cpan is to perl. Edin