RE: [PEAR] PEAR organization best practice - have files, will install?

I just want to make sure I understand you. >Martin said: >There are some packages in /pear that are not >recent in comparison to the same code in /php/pear (DB e.g.). I was originally speaking of the ~4.9 meg CVS folder pear (C:\cvsroot\pear) , not the ~1 meg CVS folder php4/pear (C:\cvsroot\php4\pear) Either way, the both of the CVS sources seem to be more recent than the PEAR that came with PHP 4.1.2 (c:\php\pear) Am I correct to assume that Tomas' instructions below are wrong, and I should only be using the scripts that came with the PHP 4.1.2 distro for production development? Tomas' instructions found at http://vulcanonet.com/soft/index.php?pack=pear_tut state "the best way to get it [PEAR], is from the CVS (the Pear DB distribution that comes with PHP is outdated, also the one that comes with PHP 4.0.6!)" I want to make sure I am using the latest and most appropriate/stable version of PEAR for development. thank you for helping me clarify this. ~ b r y a n >-> bryan >->My question is: It is best practice to drop the complete >->repository I got through CVS on top of my PHP/PEAR directory? >->With updated versions found in /PEAR , won't combining this with >->the files already found in PHP/PEAR overwrite already stable code >->with more recent versions? > Martin >For now I suggest to work with two different directories: >One directory contains the code that comes with the PHP distribution >and the other one contains the code from PEAR CVS. >When the installer code for Windows works stable, you can >install from PEAR without having to check out the sources >from CVS. >There are some packages in /pear that are not recent in comparison >to the same code in /php/pear (DB e.g.).