RE: [PEAR-DEV] [PEAR2 CS] Channel in paths

> Keep in mind, there's no requirement to use PEAR coding standards for packages on other channels. Exactly, and not using them would only increase the chances of collisions in the PHP folder. > This is incorrect, PHPUnit for example, as well as pecl packages. This > happens both when packages move from one channel to another, or are > replaced by others. That kind of conflict is irresolvable either way, since the PHP/extension folder would be in conflict. > These packages use the same name, but are distributed from different channels: > Yaml, Config, Gearman, Zend, PHPUnit, Translator, Routing, Autoload, REST_Client etc etc. But are they in conflict within the PHP folder too? In other words, with the way Pyrus is currently set up, could you install any of these packages from all channels it is distributed from without problems? If you can't install them successfully, then the channel folder wouldn't help unless it also applies in the PHP folder. (In the case of PHPUnit, AFAIK, installation will fail exactly because of that) The only scenario where the current setup helps is if these packages, while naming themselves in this way also put themselves in a vendor named folder that is different across the channels. So I guess the real question is do they do just that?