Subpackages in PEAR2

Hello all, If you don't mind, and in spite of my very limited role in PEAR, I would like to react on Travis'"PEAR2 Naming Standards" (http://wiki.pear.php.net/index.php/PEAR2_Naming_Standards) IMO, a "subpackage" is not necessarily a package for "drivers" (like it is in MDB2), nor a kind of "small PEAR Package" that would deserve its own SVN repository. The PEAR package that I am maintaining contains subpackages for example, but these are just plain containers, and I don't need multiple SVN repositories. Look at large OO applications: they can have three, four, five subpackaging levels, containing lots of classes and subpackages each, and there is only one global SVN repository for the whole code. So, if I am allowed to make a suggestion, regarding the "PEAR2 svn:externals problem", why not just refactoring the MDB2 drivers as full PEAR packages? This is how "Structures_DataGrid" proceeds with its different renderer and datasource implementations, BTW. I am sure there is no real need for a specific subpackage autoloader, in PEAR2, nor for any complex ::/_ delimiters recipe, which would awkwardly reintroduce the underscore, and perpetuate the semi-logical PEAR1 style. These were my two cents - thanks for your attention. :) Baptiste