Re: HTTP_Upload
| From: | Luc Saint-Elie | Date: | Tue, 02 Apr 2002 15:19:59 +0000 |
| Subject: | Re: HTTP_Upload | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-5171@lists.php.net to get a copy of this message | ||
At 17:11 02/04/02 +0200, Martin Jansen wrote:
But by the way the double version between /pear and php4/pear are a real problem, its the same with DB.php As it has been said numerous times on this list: The DB package in /pear is for testing only.Martin, I absolutely don't want to start a flame or to criticize anyone, I'm a PAER very happy end user, but there are "test" directories (ie /php4/pear/tests) in Pear, and it is not really easy to distinguish between "test" directories that are test, "BD" directories that are real code and "DB" directories that are tests... (php4/pear/DB.php is ver 1.87 while / pear/DB/DB.php is ver 1.1). At 18:04 02/04/02 +0300, Mika Tuupola wrote:
http://cvs.php.net/co.php/pearweb/doc/pear_package_manager.txt http://pear.php.net/faq.phpIf a newcomer reads the fact (what I did) it will understand the opposite : "The first elements of PEAR were stored in the directory php4/pear and so they were bundled with each new PHP release. For future releases of PEAR this isn't workable because PEAR will become to big to be bundled with every release of PHP. So there was a decision to commit all new elements to an own top level directory pear. The other elements which are currently remaining in php4/pear will be moved to the new top level directory soon. Only the PEAR base classes which are needed by most PEAR elements and the installer system will remain in php4/pear and will be bundled with every new release automatically. " In the case of BD the newer is in php4/pear.... Luc