Re: PEAR2 package naming standards (namespace usage)
| From: | Travis Swicegood | Date: | Thu, 28 Aug 2008 00:36:57 +0000 |
| Subject: | Re: PEAR2 package naming standards (namespace usage) | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-50670@lists.php.net to get a copy of this message | ||
On Aug 27, 2008, at 7:20 PM, Joshua Eichorn wrote:
The proposal as written would imply: /usr/lib/php/pear2/structures_datagrid/ /usr/lib/php/pear2/structures_datagrid_renderer_html/ But if you were going to just release one package and use a sub-namespace you should do: /usr/lib/php/pear2/structures/datagrid/ /usr/lib/php/pear2/structures/datagrid/renderer/html. Travis, your feedback on this item is appreciated.Both are correct. If you're releasing separate packages for drivers like MDB2 does, you would create new top-level packages, but this only applies if you are going to package your drivers separately. There are instances where that is not necessary. For example, the current Facebook wrapper uses a driver implementation to handle all of the sub-routines for the various sections of the FB API. There is no need for that separation with something so coupled. That said, the option is always available should the package maintainer and collective decide that is the best way to package the API. -T