RE: [PEAR-DEV] @package overhaul in PEAR RFC

> From: Greg Beaver [mailto:greg@chiaraquartet.net] > Sent: Monday, February 24, 2003 10:36 PM > I'd like to propose a major re-organization of both PEAR and the PHPDoc > comments. Basically, it would make a great deal of sense to re-organize > the > CVS of PEAR into the same categories that its documentation is organized > into. The impact on individual developers would of course be somewhat > minimal, but I know how hard it is to move directory structures in CVS. I also think that such a structure would be more intuitive for users. This is what the faq has to say about this (http://pear.php.net/manual/en/faq.flat-structure.php): Why a flat directory structure instead of a deep? Answer written by Stig Bakken. In CVS, PEAR code is organized by package instead of hierarchical like it would finally be installed. For example, if you want to use the XML_RPC class, you include "XML/RPC.php". It's easy to think that in CVS, this file should be in pear/XML/RPC.php, but that's not the case. XML_RPC is an independent package with its own directory in CVS, in this case the RPC.php file is actually located at pear/XML_RPC/RPC.php. The package description file (package.xml) is used to say where the files should finally be installed. The reason CVS is organized this way is that it makes package administration much easier. Regards, Lukas