[PEAR2 CS] Channel in paths

When using the Pyrus make command and installing the resulting package, I noticed that my test and doc files end up within a channel directory and only then with the package name. The PEAR2 coding standards talk only about data files. I'm assuming this part is meant to apply for test and doc files too, but regardless, I want to ask what is the rationale behind that? If the rationale is prevention of conflicts with packages from other channels, this doesn't really help unless the folder with role="php" files also uses a channel. I mean, if you try to install packages from two channels with the same name, the sources would be in conflict, so the data/doc/test/www files are the least of your problems. Besides, since PEAR2 packages are supposed to have "PEAR2_" as a prefix for their name, I don't see how conflicts could really arise. PEAR1 packages don't have that prefix, so they can both coexist, so that can't be the rationale either. Unless there's some better reason I'm missing, I'd like to propose for the implicit directory structure to be changes so that "ROLE" files are located at "ROLE_dir/PackageName/" ("ROLE" being anything other than 'role="php"' files), and that PHP files are explicitly clarified to be in "any-mypear-folder/fully-qualified-class-to-directory-converted-name" (unless I've misunderstood that, and they too are supposed to be in "any-mypear-folder/channel/fully-qualified-class-to-directory-converted-name "). Regards, Vasil Rangelov