Re: [PEPr] Changes in proposal for RFC::Prefix all packages with P_
| From: | Scott Mattocks | Date: | Wed, 04 Oct 2006 12:19:39 +0000 |
| Subject: | Re: [PEPr] Changes in proposal for RFC::Prefix all packages with P_ | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-44303@lists.php.net to get a copy of this message | ||
Markus Tacker wrote:
Markus Tacker (http://pear.php.net/user/tacker) has edited the proposal for RFC::Prefix all packages with P_. Change comment: * We now target for PEAR_ as the prefixI know it is too late (I have a tendency to not think of some things until after the vote starts for some reason), but it was never discussed how this effects the directory structure rules. Example: PEAR_Frontend_Web is in directory PEAR/Frontend Does the new naming scheme mean that everything has to be in the PEAR directory? PEAR_Services_SomeService_Driver should probably still live in Services/SomeService but now the naming is all confusing. And how do I know which classes are in the PEAR group and which are just part of a PEAR package? Again, sorry for bringing this up so late but it just came to me and I need at least a little discussion before I vote. Thanks, Scott